3.5 Service Pack 1 (3.5 SP1)
- 1 Updates and fixes in this service pack (3.5 SP1)
- 2 Installation Process
- 2.1 Scenario 1: If you are deploying SC 3.5 for the first time with this service pack (or starting from scratch)
- 2.1.1 Linux / Windows
- 2.2 Scenario 2: If you are already running SC 3.5 and upgrading to this 3.5 SP1 release
- 2.3 Scenario 3: If you are already running SC 3.4 SP3 and upgrading to this 3.5 SP1 release
- 2.3.1 Linux / Windows
- 2.1 Scenario 1: If you are deploying SC 3.5 for the first time with this service pack (or starting from scratch)
- 3 Verification
Updates and fixes in this service pack (3.5 SP1)
Syndeia Cloud 3.5 SP1, including the REST API and the Syndeia Cloud Web Dashboard, has several improvements which are listed here: Syndeia 3.5 SP1 - Improvements.
Installation Process
Syndeia Cloud 3.5 SP1 is a full build of Syndeia Cloud and not a patch/incremental build. It is an in-place upgrade of the Syndeia Cloud services and does NOT require any data migration. Follow the steps below to deploy Syndeia Cloud 3.5 SP1.
Download & extract the three
.zip
files to your home dir, i.e.syndeia-cloud-3.5-SP1.zip
,syndeia-cloud-3.5-SP1_janusgraph.zip
,syndeia-cloud-3.5-SP1_cassandra_zookeeper_kafka_setup.zip
Identify your current Syndeia Cloud version and platform (Windows, Linux). The version can be identified by checking the Help > About menu in Syndeia Cloud.
Follow the instructions below for the scenario and platform relevant to your environment.
Scenario 1: If you are deploying SC 3.5 for the first time with this service pack (or starting from scratch)
Linux / Windows
Gather the three
.zip
files you downloaded for Syndeia Cloud 3.5 SP1 and follow the instructions here: Deployment
Scenario 2: If you are already running SC 3.5 and upgrading to this 3.5 SP1 release
Linux
To upgrade Syndeia Cloud (SC) to 3.5 SP1: in your
bash
shell, run the below and follow the prompts:export SC_snapshot_version_old=3.5 cd ~/syndeia-cloud-3.5-SP1/bin/ ./syndeia-cloud-3.5_install.bash --upgrade -s -SC_v 3.5-SP1
Note, if you are running a multi-node configuration you will also need to pass in
--multi_node
(or-m
), ie:export SC_snapshot_version_old=3.5 cd ~/syndeia-cloud-3.5-SP1/bin/ ./syndeia-cloud-3.5_install.bash --upgrade -s --multi_node --SC_version=3.5-SP1
Windows
Stop all existing SC services via
services.msc
(SCM)To upgrade Syndeia Cloud (SC) to 3.5 SP1: in a Cygwin/WSL terminal, run the below and follow the prompts:
export SC_snapshot_version_old=3.5 cd ~/syndeia-cloud-3.5-SP1/bin/ ./syndeia-cloud-3.5_install_windows.bash --upgrade -s -SC_v 3.5-SP1
Note, if you are running a multi-node configuration you will also need to pass in
--multi_node
(or-m
), ie:export SC_snapshot_version_old=3.5 cd ~/syndeia-cloud-3.5-SP1/bin/ ./syndeia-cloud-3.5_install_windows.bash --upgrade -s --multi_node --SC_version=3.5-SP1
Scenario 3: If you are already running SC 3.4 SP3 and upgrading to this 3.5 SP1 release
Linux / Windows
Please follow the instructions on the Migration page but use SC 3.5 SP1 everywhere where it references SC 3.5.
Verification
Scenario 2 ONLY: Confirm
batch_size_warn_threshold_in_kb
andbatch_size_fail_threshold_in_kb
in/etc/cassandra/default.conf/cassandra.yaml
have been bumped up from their defaults, ex:batch_size_warn_threshold_in_kb: 250 batch_size_fail_threshold_in_kb: 300
If you make changes to the above, restart the Cassandra service:
sudo systemctl restart cassandra
If you frequently deal with large artifact sizes you may want to configure your monitoring to watch for the “batch size” warn messages and bump up as needed.
Scenario 2 ONLY: Make sure sc-store service’s
application.conf
at/opt/icx/syndeia-cloud-current/store-impl-3.5-SP1/conf/application.conf
contains the following performance tuning enhancements on ~L95:cassandra-query-journal { refresh-interval = 25ms # added events-by-tag nesting during lagom upgrade to 1.6.5 (to cater to akka persistence cassandra migration to 0.80) # https://doc.akka.io/docs/akka-persistence-cassandra/0.101/migrations.html events-by-tag { # Turn off the eventual consistency delay eventual-consistency-delay = 50ms # Turn on event by persistence id tracking, this timeout is the maximum amount of time that akka-persistence-cassandra will hold off publishing an event when missed events are detected # changed name from delayed-event-timeout to gap-timeout during lagom upgrade to 1.6.5 (to cater to akka persistence cassandra migration to 0.80) # https://doc.akka.io/docs/akka-persistence-cassandra/0.101/migrations.html gap-timeout = 30s flush-interval = 25ms first-time-bucket = "20221101T00:00" } }
If not, add them and restart the sc-store service.
sudo systemctl restart sc-store
Follow the steps in the section Validating Syndeia Cloud Installation & Configuration on the following page to verify your installation: