Upgrading SENTIENT to 3.2.2
NOTE: These upgrade steps are applicable for SENTIENT version 3.2.1. In order to upgrade to 3.2.2 you need to upgrade to 3.2.1 first.
NOTE: Since SENTIENT version 3.2.2 Java 11 is used
- Please install Java 11 before proceeding upgrade procedure using the following guide:
Please note that Cassandra 4.x is still in beta. SENTIENT is compatible with Cassandra 3.x as well. However, since SENTIENT 3.2.2+ requires Java 11 and Cassandra 3.x is not compatible with Java 8, you can’t launch SENTIENT 3.2.2+ and Cassandra 3.x on the same machine without separate docker containers for both..
Please consider using docker compose or other cluster setup to avoid issues with beta version of Cassandra.
SENTIENT package download
1
wget https://github.com/sentient/sentient/releases/download/v3.2.2/sentient-3.2.2.rpm
SENTIENT service upgrade
- Stop SENTIENT service if it is running.
1
$ sudo service sentient stop
1
sudo rpm -Uvh sentient-3.2.2.rpm
NOTE: Package installer will ask you to merge your sentient 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/sentient/conf/sentient.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)
Execute regular upgrade script:
1
sudo /usr/share/sentient/bin/install/upgrade.sh --fromVersion=3.2.1
Start the service
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
1
sudo service sentient start
Upgrading SENTIENT to 3.2.1
NOTE: These upgrade steps are applicable for SENTIENT version 3.2. In order to upgrade to 3.2.1 you need to upgrade to 3.2 first.
SENTIENT package download
1
wget https://github.com/sentient/sentient/releases/download/v3.2.1/sentient-3.2.1.rpm
SENTIENT service upgrade
- Stop SENTIENT service if it is running.
1
$ sudo service sentient stop
1
sudo rpm -Uvh sentient-3.2.1.rpm
NOTE: Package installer will ask you to merge your sentient 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/sentient/conf/sentient.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)
Execute regular upgrade script:
1
sudo /usr/share/sentient/bin/install/upgrade.sh --fromVersion=3.2.0
Start the service
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
1
sudo service sentient start
Upgrading SENTIENT to 3.2
NOTE: These upgrade steps are applicable for SENTIENT version 3.1.1. In order to upgrade to 3.2 you need to upgrade to 3.1.1 first.
SENTIENT package download
1
wget https://github.com/sentient/sentient/releases/download/v3.2/sentient-3.2.rpm
SENTIENT service upgrade
- Stop SENTIENT service if it is running.
1
$ sudo service sentient stop
1
sudo rpm -Uvh sentient-3.2.rpm
NOTE: Package installer will ask you to merge your sentient 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/sentient/conf/sentient.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)
Execute regular upgrade script:
1
sudo /usr/share/sentient/bin/install/upgrade.sh --fromVersion=3.1.1
Start the service
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
If you use Redis for caching, you need to flush all stored keys before starting the SENTIENT.
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 SENTIENT. If other applications use Redis, you need to locate the SENTIENT database and flush only that. The default database index is 0, configurable with REDIS_DB SENTIENT environment value.
redis-cli
select 0
flushdb
1
sudo service sentient start