Timeline for Cassandra 4.0.5 nodes fails to start when replacing dead node
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2023 at 14:36 | answer | added | Paul | timeline score: 1 | |
| Aug 29, 2023 at 12:02 | comment | added | anshul | We are on GCP cloud and and using K8s for managing infra, so chances are minimal of having security issues as the same settings are working for other nodes. It might be we are hitting some edge case scenario as in the bug CASSANDRA-16877 (this was fixed in 4.0.1 version) and we are at 4.0.5. | |
| Aug 19, 2023 at 14:44 | comment | added | Aaron | How are you deploying your nodes? It looks like the new node cannot reach the cluster on port 7000. Is it possible that sometimes security configs for the new node don't propagate right away? That's the only reason I can think of there a terminate/redeploy of a replacement node would fix anything. | |
| Aug 18, 2023 at 12:31 | history | edited | John K. N. | CC BY-SA 4.0 |
formatted question;
|
| S Aug 16, 2023 at 18:29 | review | First questions | |||
| Aug 18, 2023 at 12:31 | |||||
| S Aug 16, 2023 at 18:29 | history | asked | anshul | CC BY-SA 4.0 |