Closed mehmetdreamgames closed 2 years ago
"This is indeed a non-standard, unsupported partitioner: com.amazonaws.cassandra.DefaultPartitioner. Token-aware routing won't work with AWS Keyspaces unless you write your own TopologyMonitor and TokenFactory."
Keyspaces now supports the standard RandomPartitioner
and can be changed at the account level via either the console or via CQL: https://docs.aws.amazon.com/keyspaces/latest/devguide/working-with-partitioners.html
We have moved our cassandra cluster to Amazon Keyspaces, in practice we did not face critical issues so far. But there's an already open discussion for
DefaultTopologyMonitor
andTokenFactory
warnings. We have facing issues related to these warnings when we attempted to use in production.Control node .../...:9142 has an entry for itself
Unsupported partitioner 'com.amazonaws.cassandra.DefaultPartitioner', token map will be empty.
We have following configuration as it's suggested by AWS experts in the discussion:
metadata { schema { enabled = false } token-map { enabled = false } }
The warnings are appearing after a period like ~24 hours without any action on our side. You can see the below chart, we have ~35k warnings coming from 10 different pods .
We are using AWS sigv4 plugin and we implemented as it's suggested in Sample Application