Depending on the amount of existing data in your Cassandra database, this may falsely report as failed (because the init script only waits a fixed amount of time for the service to start). Perform the next step below to determine the real status. If you do not get the indicated result, submit the start service command again, and if the desired result still does not result, check logs at /var/log/msys-cassandra/ for error messages.

After Cassandra starts, check that the database has been replicated (UN means Up Normal) using service msys-cassandra status or /opt/msys/3rdParty/cassandra/bin/nodetool status. You should expect to see the new node participating in the Cassandra cluster.

# Update the following file by ADDING the new Platform host to the "cassandra:hosts" array
# /opt/msys/app/users-api/config/production.json
# Example:
# Add this line below the former last-node line: "node4.int.messagesystems.com"
# You must also add a trailing comma at the end of the former last-node line.
{
"cassandra": {
"hosts": [
"node1.int.messagesystems.com",
"node2.int.messagesystems.com",
"node3.int.messagesystems.com"
]
}
}
# Update the following file by ADDING the new Platform host to the "cql:contactPoints" array
# /opt/msys/app/webhooks-api/config/production.json
# Example:
# Add this line below the former last-node line: "node4.int.messagesystems.com"
# You must also add a trailing comma at the end of the former last-node line.
{
"cql": {
"contactPoints": [
"node1.int.messagesystems.com",
"node2.int.messagesystems.com",
"node3.int.messagesystems.com"
]
}
}

Restart all applicable services.

service msys-app-users-api restart
service msys-app-webhooks-api restart
service msys-nginx reload