Please note that Cassandra 4.x is still in beta. ThingsBoard is compatible with Cassandra 3.x as well. However, since ThingsBoard 3.2.2+ requires Java 11 and Cassandra 3.x is not compatible with Java 8, you can’t launch ThingsBoard 3.2.2+ and Cassandra 3.x on the same machine without separate docker containers for both..
NOTE: Package installer will ask you to merge your thingsboard configuration. It is preferred to use merge option to make sure that all your previous parameters will not be overwritten.
Please make sure that you set database.ts.type parameter value (in the file /etc/thingsboard/conf/thingsboard.yml) to “cassandra” instead of “sql” if you are using Cassandra database for timeseries data:
1
2
3
4
database:
ts_max_intervals: "${DATABASE_TS_MAX_INTERVALS:700}" # Max number of DB queries generated by single API call to fetch telemetry records
ts:
type: "${DATABASE_TS_TYPE:sql}" # cassandra, sql, or timescale (for hybrid mode, DATABASE_TS_TYPE value should be cassandra, or timescale)
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
1
sudo service thingsboard start
Upgrading ThingsBoard CE to 3.2.1
NOTE: These upgrade steps are applicable for ThingsBoard version 3.2. In order to upgrade to 3.2.1 you need to upgrade to 3.2 first.
NOTE: Package installer will ask you to merge your thingsboard configuration. It is preferred to use merge option to make sure that all your previous parameters will not be overwritten.
Please make sure that you set database.ts.type parameter value (in the file /etc/thingsboard/conf/thingsboard.yml) to “cassandra” instead of “sql” if you are using Cassandra database for timeseries data:
1
2
3
4
database:
ts_max_intervals: "${DATABASE_TS_MAX_INTERVALS:700}" # Max number of DB queries generated by single API call to fetch telemetry records
ts:
type: "${DATABASE_TS_TYPE:sql}" # cassandra, sql, or timescale (for hybrid mode, DATABASE_TS_TYPE value should be cassandra, or timescale)
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
1
sudo service thingsboard start
Upgrading ThingsBoard CE to 3.2
NOTE: These upgrade steps are applicable for ThingsBoard version 3.1.1. In order to upgrade to 3.2 you need to upgrade to 3.1.1 first.
NOTE: Package installer will ask you to merge your thingsboard configuration. It is preferred to use merge option to make sure that all your previous parameters will not be overwritten.
Please make sure that you set database.ts.type parameter value (in the file /etc/thingsboard/conf/thingsboard.yml) to “cassandra” instead of “sql” if you are using Cassandra database for timeseries data:
1
2
3
4
database:
ts_max_intervals: "${DATABASE_TS_MAX_INTERVALS:700}" # Max number of DB queries generated by single API call to fetch telemetry records
ts:
type: "${DATABASE_TS_TYPE:sql}" # cassandra, sql, or timescale (for hybrid mode, DATABASE_TS_TYPE value should be cassandra, or timescale)
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the ThingsBoard.
Connect to your Redis instance (or container/pod, depending on your setup) and run the command:
redis-cli flushall
Please note that this command is applicable only if you use Redis exclusively for ThingsBoard. If other applications use Redis, you need to locate the ThingsBoard database and flush only that. The default database index is 0, configurable with REDIS_DB ThingsBoard environment value.
redis-cli
select 0
flushdb
1
sudo service thingsboard start
Our website uses cookies to ensure site security and optimize your experience on our website. By continuing to browse this site, you agree to the use of these cookies, in accordance with our Cookie Policy. For details on managing cookies, please adjust your browser settings.