Upgrading SENTIENT to 3.1.1
NOTE: These upgrade steps are applicable for SENTIENT version 3.1. In order to upgrade to 3.1.1 you need to upgrade to 3.1 first.
SENTIENT package download
Download SENTIENT installation archive for Windows: sentient-windows-3.1.1.zip.
SENTIENT service upgrade
- Stop SENTIENT service if it is running.
1
net stop sentient
-
Make a backup of previous SENTIENT configuration located in <SENTIENT install dir>\conf (for ex. C:\sentient\conf).
- Remove SENTIENT install dir.
- Unzip installation archive to SENTIENT install dir.
- Compare your old SENTIENT configuration files (from the backup you made in the first step) with new ones.
- Please make sure that you set database.ts.type parameter value (in the file <SENTIENT install dir>\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)
- Finally, run upgrade.bat script to upgrade SENTIENT to the new version.
NOTE Scripts listed above should be executed using Administrator Role.
Execute regular upgrade script:
1
C:\sentient>upgrade.bat --fromVersion=3.1.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
net start sentient
Upgrading SENTIENT to 3.1
NOTE: These upgrade steps are applicable for SENTIENT version 3.0.1. In order to upgrade to 3.1 you need to upgrade to 3.0.1 first.
SENTIENT package download
Download SENTIENT installation archive for Windows: sentient-windows-3.1.zip.
SENTIENT service upgrade
- Stop SENTIENT service if it is running.
1
net stop sentient
-
Make a backup of previous SENTIENT configuration located in <SENTIENT install dir>\conf (for ex. C:\sentient\conf).
- Remove SENTIENT install dir.
- Unzip installation archive to SENTIENT install dir.
- Compare your old SENTIENT configuration files (from the backup you made in the first step) with new ones.
- Please make sure that you set database.ts.type parameter value (in the file <SENTIENT install dir>\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)
- Finally, run upgrade.bat script to upgrade SENTIENT to the new version.
NOTE Scripts listed above should be executed using Administrator Role.
NOTE: If you were using Cassandra database for entities data execute the following migration script:
1
C:\sentient>upgrade.bat --fromVersion=cassandra-latest-to-postgres
Execute regular upgrade script:
1
C:\sentient>upgrade.bat --fromVersion=3.0.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
net start sentient