I would check whether some SSTables are marked as repaired while others are not (by running sstablemetadata and checking the value of repairedAt).
An inconsistency in the repaired state, it might explain overstreaming. During repairs, data from repaired SSTables on one node is only compared with data from repaired SSTables on other nodes and data from unrepaired SSTables on one node is only compared with data from unrepaired SSTables on other nodes. So if the same data is marked as repaired on some but not all nodes, it might lead to this data being streamed, even though it is actually already present – just in the other set of SSTables. > Am 23.01.2024 um 19:07 schrieb manish khandelwal > <manishkhandelwa...@gmail.com>: > > In one of our two datacenter setup(3+3), one Cassndra node is getting lot of > data streamed from other nodes during repair to the extent that it fills up > and ends with full disk. I am not able to understand what could be the reason > that this node is misbehaving in the cluster. Cassandra version is 3.11.2 > > System logs show every node sending data to this node.Any pointer where > should I look at would be helpful. > > Regards > Manish
smime.p7s
Description: S/MIME cryptographic signature
