All ports are open.
We tried rolling restart and full cluster down and start one mode at a time.
Changes down were:
Storage addition
Ddl for column drop and recreate
Schema version is same for few nodes and few shows unavailable.
Network has been verified in detail and no severe packet drops.
Ideas that come mind are:
- Rolling restart of the cluster
- Use of 'nodetool resetlocalschema' --> function name speaks for itself.
Note that this is to be ran on each node you think is having schema issues
- Are all nodes showing a schema version showing the same one?
- Port not fully open
Thank you Alain.
Nodetool describecluster shows some nodes unreachable, different output from
each node.
Node1 can see all 4 nodes up.
Node 2 says node 4 and node 5 unreachable
Node 3 complains about node node 2 and node 1
Nodetool status shows all nodes up and read writes are working for most
Hello Nitan,
1. Can sstable corruption in application tables cause schema mismatch?
>
I would say it should not. I could imagine in the case that the corrupted
table hits some 'system' keyspace sstable. If not I don' see how corrupted
data can impact the schema on the node.
> 2. Do we need to
Hi,
Two questions:
1. Can sstable corruption in application tables cause schema mismatch?
2. Do we need to disable repair while adding storage while Cassandra is down?
Regards,
Nitan
Cell: 510 449 9629
