Release version

Legacy version are available here: https://archive.apache.org/dist/iotdb/

Attention:

• Recommended OS parameters

  • Set the somaxconn as 65535 to avoid “connection reset” error when the system is under high load.

    # Linux
    > sudo sysctl -w net.core.somaxconn=65535
    
    # FreeBSD or Darwin
    > sudo sysctl -w kern.ipc.somaxconn=65535
    

• How to upgrade a minor version (e.g., from v0.11.0 to v0.11.3)?

  • versions which have the same major version are compatible.
  • Just download and unzip the new version. Then modify the configuration files to keep consistent with what you set in the old version.
  • stop the old vesion instance, and start the new one.

• How to upgrade from v.11.x or v0.10.x to v0.12.x?

  • Upgrading from v0.11 or v0.10 to v0.12 is similar as v0.9 to v0.10. The upgrade tool will rewrite the data files automatically.
  • Stop writing new data.
  • Call flush command using sbin/start-cli.sh in original version to close all TsFiles.
  • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
  • Just download, unzip v0.12.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in previous version (or the backup folder). You can also modify other settings if you want. Any other config changes in v0.11 should be moved to v0.12.
  • Stop IoTDB v0.11 or v0.10 instance, and start v0.12.x, then the IoTDB will upgrade data file format automatically. It is ok to read and write data when the upgrading process works.
  • After a log All files upgraded successfully! printed, the upgrading completes.
  • NOTICE 1: V0.12 changes many settings in conf/iotdb-engine.properties, so do not use previous configuration file directly.
  • NOTICE 2: V0.12 doesn't support upgrade from v0.9 or lower version, please upgrade to v0.10 first if needed.
  • NOTICE 3: We don't recommend to delete data before the upgrading finished. The deletion will fail if you try to delete data in the storage group with upgrading files.

• How to upgrade from v.10.x to v0.11.x?

  • The data format (i.e., TsFile data) of v0.10.x and v0.11 are compatible, but the WAL file is incompatible. So, you can follow the steps:
  • Stop writing new data.
  • Call flush command using sbin/start-cli.sh in v0.10.x to close all TsFiles.
  • We recommend to backup the the wal files and mlog.txt before upgrading for rolling back.
  • Just download, unzip v0.11.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the data folder set in v0.10.x (or the backup folder). You can also modify other settings if you want.
  • Stop IoTDB v0.10.x instance, and start v0.11.x, then the IoTDB will upgrade data file format automatically.
  • NOTICE: V0.11 changes many settings in conf/iotdb-engine.properties, so do not use v0.10's configuration file directly.

• How to upgrade from v0.9.x to v0.10.x?

  • Upgrading from v0.9 to v0.10 is more complex than v0.8 to v0.9.
  • Stop writing new data.
  • Call flush command using sbin/start-client.sh in v0.9 to close all TsFiles.
  • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
  • Just download, unzip v0.10.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in v0.9.x (or the backup folder). You can also modify other settings if you want.
  • Stop IoTDB v0.9 instance, and start v0.10.x, then the IoTDB will upgrade data file format automatically.

• How to upgrade from 0.8.x to v0.9.x?

  • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
  • Just download, unzip v0.9.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in v0.8.x (or the backup folder). You can also modify other settings if you want.
  • Stop IoTDB v0.8 instance, and start v0.9.x, then the IoTDB will upgrade data file format automatically.

All releases

Find all releases in the Archive repository.

Verifying Hashes and Signatures

Along with our releases, we also provide sha512 hashes in *.sha512 files and cryptographic signatures in *.asc files. The Apache Software Foundation has an extensive tutorial to verify hashes and signatures which you can follow by using any of these release-signing KEYS .