cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Relish Chackochan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9184) sstable.CorruptSSTableException
Date Tue, 14 Apr 2015 05:00:18 GMT

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

Relish Chackochan updated CASSANDRA-9184:
-----------------------------------------
    Environment: Apache Cassandra 1.2.16 on RHEL 6.5  (was: Cassandra 1.2.16 on RHEL 6.5)

> sstable.CorruptSSTableException
> -------------------------------
>
>                 Key: CASSANDRA-9184
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9184
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Apache Cassandra 1.2.16 on RHEL 6.5
>            Reporter: Relish Chackochan
>
> We have 8 node Cassandra cluster with 1.2.16 version (  RHEL 6.5 64-bit ) on Vmware ESXi
server and having SSTable Corrupt Error facing frequently on multiple columfamily. Using "nodetol
scrub" i am able to resolve the issue. i would like to know why this is happening frequently.
is this related to any configuration parameters or VMware related issue.
> Can someone help on this.
> org.apache.cassandra.io.sstable.CorruptSSTableException: java.io.IOException: dataSize
of 3691036590893839668 starting at 362204813 would be larger than file /opt/lib
> /cassandra/data/XXXXX/XXXXXX/XXXX-XXXXX-ic-1144-Data.db length 486205378



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message