Preview Tool

Cisco Bug: CSCut34885 - Removed COS node carry previous cassandra node after it joins to new PAM

Last Modified

Aug 20, 2015

Products (1)

  • Cisco Content Delivery Engine Series

Known Affected Releases


Description (partial)

1. 2 COS nodes in a cluster: A & B
2. Remove cos node B from the PAM1 cluster. 
3. Register the removed cos node B to the PAM2 cluster.
4. When the cassandra DB is up on the cos node B, it is observed that "nodetool status" still lists cos node A.

Node B's cassandra.yaml still lists Node A as a seed.

Node A & B were initially registered to same PAM (PAM1), AND
PAM1 & PAM2 are on the same network, AND
Node B is removed from PAM1 and added to PAM2, AND
Node B's cassandra.yaml file still lists node A's IP as a seed
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.