Preview Tool

Cisco Bug: CSCur92063 - cassandra db-remove mechanism issue

Last Modified

Mar 10, 2018

Products (1)

  • Cisco Content Delivery Engine Series

Known Affected Releases


Description (partial)

COS node is not part of cluster in COS GUI, but is still part of Cassandra cluster and Cassandra is running on the node.

AIC Client log suggests that when node was removed from cluster in GUI, AIC Client attempted to initialize DB on that node.

When a node is added to a cluster using COS GUI, Cassandra DB is attempted to be initialized on it.

If the initialization fails, the db-init flag marking that the DB has been successfully initialized will not be set. 

Later, if the node is attempted to be removed from the cluster using the COS GUI, cassandra-init script may still get launched thinking that DB has not been initialized before (since flag is not set).

If cassandra-init script succeeds this time, it may leave the COS node in a state where Cassandra DB is initialized and started on the node, and the node is still part of the DB cluster, even though it is not part of COS cluster.

AIC Client log may contain messages:

DB running
Done initializing DB
[2014-11-27 21:13:24.478] [INFO] aicc - db-init exited normally
[2014-11-27 21:13:24.478] [INFO] aicc - Done writing dbinitflag
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.