> It is surprising to me that we load the identity from the keystore vs > explicitly setting an expected value in cassandra.yaml. I get that an error > is thrown if the identity doesn't match those of other nodes in the cluster, > but does it make sense to prevent startup should the value in the keystore > deviate from a (currently nonexistent) value in cassandra.yaml?
We can make it optionally configurable. The concern about adding identities in a yaml is that it generally requires a bounce for Cassandra to pick up new values. > It feels like there is a parallel to how we set the cluster name in > cassandra.yaml even though the value is also present within our local > sstables and leads to startup errors should they differ. I can see the parallels here. Thanks for the feedback. Dinesh
