[
https://issues.apache.org/jira/browse/CASSANDRA-15275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913265#comment-16913265
]
Sumit commented on CASSANDRA-15275:
-----------------------------------
Can some please update me what are reasons for data corruption?.
> Repair failed due to data corruption in one of the production table
> -------------------------------------------------------------------
>
> Key: CASSANDRA-15275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15275
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Sumit
> Priority: Normal
> Attachments: cassandra_repair_logs
>
>
> Issue description:
> We found data corruption in one of table, while performing cluster syncing.
>
> Corrective actions:
> We have performed 'nodetool repair' to sync up the nodes, post removing the
> corrupted table. There were two, out of four node, in the cluster was down
> before we triggered the 'repair'. However, during the repair all the servers
> were live and active.
>
> We are using Cassandra 3.11.1.
> Appreciate your help to pinpoint the issue, and let me know reasons to data
> corruption in table and how we can prevent it?
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
