Troubleshooting
Problem
One cassandra pod would not complete initialisation, but the oc logs command did not show any errors or warnings that didn't also appear in the pods that came up OK.
Symptom
While it is in this state, it is not possible to truncate tables to reduce the space usage (even if the number of pods was reduced to 2 or 1), the following message was received:
"Cannot achieve consistency level ALL"
"Cannot achieve consistency level ALL"
Resolving The Problem
Connect to the pod and removed ALL the commit logs from:
/opt/ibm/cassandra/data/commitlog
on the failing cassandra pod and restart it.
It should then come up ok.
Login to a pod and run: nodetool repair to fix the schema warnings (Warning: schema version mismatch detected).
Note: The removal of the commit log will result in some loss of data.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTPTP","label":"Netcool Operations Insight"},"ARM Category":[{"code":"a8m0z0000001jZTAAY","label":"NOI Netcool Operations Insights-\u003ECNEA Cloud Native Event Analytics"}],"ARM Case Number":"TS013332876","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
22 June 2023
UID
ibm17006095