Thanks Bowen and Sebastian . That is good information. I am still figuring
out what could have gone wrong. Will update here once I get something.
Regards
Manish
On Wed, Jan 24, 2024 at 3:40 PM Bowen Song via user <
user@cassandra.apache.org> wrote:
> Some common causes of over-streaming:
>
>
Some common causes of over-streaming:
* "repair_session_space" is too small (either manually specified, or
heap size is small and data on disk is large)
* Manually deleting SSTable files
* Unexpected foreign (e.g. from a backup) SSTable files
* Marking SSTable as repaired or unrepaired inc
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 wit
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
