casandra issue

Owned by Jean-luc KRIKER
Last updated: Dec 09, 2018
1 min read


if the node goes off line ( casandra db)  for a time greater than the "gc_grace_seconds as per"  casandra database may not come back.


https://github.com/Juniper/contrail-controller/wiki/Recovery-procedure-when-contrail-database-is-down-for-greater-than-gc_grace_seconds


contrail-status

. . . . 

== Contrail Database ==

contrail-database:            inactive

. . . 


cassandra logs – any


2017-08-01 02:37:03,727 - ERROR - FAILED: nodetool -h 127.0.0.1 info | grep ID | awk '{print $3}'

2017-08-01 02:37:03,727 - ERROR - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused (Connection refused)'.

2017-08-01 02:37:03,728 - DEBUG - run_command: service contrail-database stop

2017-08-01 02:37:03,739 - DEBUG - SECS SINCE UP: 1097393


Solution for a single controller:

delete and restart

rm /var/log/cassandra/status-up

service contrail-database start.