Upgrade-RHOP-R4.1.1.1 to R4.1.2 build-19 cassandra failed to come up on analyticsdb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Invalid
|
High
|
alexey-mr | ||
R4.1 |
Fix Committed
|
High
|
alexey-mr |
Bug Description
analyticsdb node cassandra service failed to come up after upgrade
After upgrading the cluster from R4.1.1 to R4.1.2, we are removing the entry 'num_tokens: 256' from cassadra.yaml causing the issue.
While we upgrade, do not remove num_token entry.
Workaround:
======
After setting 'num_tokens: 256' in /etc/cassandra/
restart service contrail-database
command: service contrail-database restart
log:
===
[main] 2018-10-29 20:16:14,806 StorageService.
INFO [main] 2018-10-29 20:16:14,904 TokenMetadata.
INFO [main] 2018-10-29 20:16:14,904 TokenMetadata.
ERROR [main] 2018-10-29 20:16:14,966 CassandraDaemon
org.apache.
at org.apache.
at org.apache.
at org.apache.
at org.apache.
at org.apache.
at org.apache.
INFO [StorageService
INFO [StorageService
INFO [StorageService
INFO [CompactionExec
information type: | Proprietary → Public |
summary: |
- Upgrade-RHOP-R4.1.1.1 to R4.1.2 build-19 cassandra failed to come up + Upgrade-RHOP-R4.1.1.1 to R4.1.2 build-19 cassandra failed to come up on + analyticsdb |
Changed in juniperopenstack: | |
assignee: | nobody → alexey-mr (alexey-morlang) |
description: | updated |
description: | updated |
Review in progress for https:/ /review. opencontrail. org/47374
Submitter: alexey-mr (<email address hidden>)