[ 
https://issues.apache.org/jira/browse/CASSANDRA-15275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit updated CASSANDRA-15275:
------------------------------
    Description: 
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?
 

  was:
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 prevent recur.
 


> 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
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to