Through OpsCenter 6.6.7, I've installed DES 6.7.7 in 3 EC2 nodes, same region (single datacenter). All seemed good, no errors, all agents in right version, everything synced in green.
Then, I changed the replication factor and strategy for all my custom keyspaces:
ALTER KEYSPACE <KeySpace> WITH replication = {'class': 'NetworkTopologyStrategy','ap-southeast-2': '3'} AND durable_writes = true;
Also, I changed 3 preinstalled keyspaces system_auth, dse_securit & dse_insights and applied same RF=3 and strategy (NetworkTopologyStrategy).
Finally, I run "nodetool repair -pr" in every node, as suggested
However, Opscenter/NodeSyn option shows: dse_insights is not synced
24% of the data was not synced before the NodeSync deadline. An increase in configured throughput is recommended.
nodetool shows:
$ nodetool status -- Address Load Tokens Owns Host ID Rack UN 10.1.18.20 1.8 GiB 8 ? 3dce59c0-0598-4f68-84d0-d3b95bb1e5d7 ap-southeast-2a UN 10.1.19.20 2.11 GiB 8 ? 10462c39-5ade-4659-b447-50045a510dbf ap-southeast-2c UN 10.1.18.148 2.43 GiB 8 ? d453b12c-c3a9-40b2-9639-08e219b85ca1 ap-southeast-2b Note: Non-system keyspaces don't have the same replication settings, effective ownership information is meaningless $ nodetool repair --full dse_insights [2020-02-26 21:55:23,501] Skipping anti-entropy repair on tables with NodeSync enabled: [dse_insights.insights_config, dse_insights.tokens]. [2020-02-26 21:55:23,503] Starting repair command #31206 (b0791580-58e2-11ea-ba93-b9f25d1473d7), repairing keyspace dse_insights with repair options (parallelism: parallel, primary range: false, incremental: false, job threads: 1, ColumnFamilies: {}, dataCenters: {}, hosts: {}, previewKind: NONE, # of ranges: 24, pull repair: false, force repair: false)
In OpsCenter I enabled the Repair tool, but no effect.
What's missing or wrong?
cassandra.yaml
- partitioner: Murmur3partitioner
- num_tokens: 8
- allocate_tokens_for_local_replication_factor: 3
- authenticator: DseAuthenticator
- autorizer: DseAutorizer
- Role_manager: DseRoleManager
Miguel