Hi all, We run some large clusters using Kubernetes and recently ran into an issue on 4.0.x, so I decided to look at 5.1 and see if TCM fixes the issue.
However what we found was there are a number of new issues with TCM when a node is stopped then restarts with a new ip address, something that happens quite often with Kubernetes, and normally works fine in 4.0 So, I have a couple of questions, firstly, I am testing against trunk, is there a better branch to test TCM? Secondly, is this stable enough that I should be raising Jira tickets for the issues, if so, should I attach them to the Epic CASSANDRA-19055 or create them standalone? Thanks Paul Chandler
