Guest

Preview Tool

Cisco Bug: CSCur99122 - Replication factor shouldn't be 3 when 3rd node failed to be added

Last Modified

Aug 11, 2017

Products (1)

  • Cisco Content Delivery Engine Series

Known Affected Releases

2.1(0)

Description (partial)

Symptom:
In AIC Client log (/arroyo/log/cos-aic-client.log), an error message is seen when trying to add a third node to a 2-node cluster, suggesting that the Cassandra database could not be successfully initialized on the new node.

However, when running cqlsh on an existing node in cluster with Cassandra running, it is determined that the replication factor still got updated to 3 ("DC1" : "3").

Conditions:
A new second (or third) node failed to be added to an existing 1-node (or 2-node) cluster; however, the replication factor still got changed to 2 (or to 3).

A node in a 3-node (or 2-node) cluster failed to be removed from an existing cluster; however, the replication factor still got changed to 2 (or 1).
Bug details contain sensitive information and therefore require a Cisco.com 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.