cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Arena (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2798) Repair Fails 0.8
Date Mon, 20 Jun 2011 13:53:47 GMT

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

David Arena updated CASSANDRA-2798:
-----------------------------------

    Description: 
I am seeing a fatal problem in the new 0.8

Im running a 3 node cluster with a replication_factor of 3..

On Node 3.. If i 
# kill -9 cassandra-pid
# rm -rf "All data & logs"
# start cassandra
# nodetool -h "node-3-ip" repair

The whole cluster become duplicated..

* e.g Before 
node 1 -> 2.65GB
node 2 -> 2.65GB
node 3 -> 2.65GB

* e.g After
node 1 -> 5.3GB
node 2 -> 5.3GB
node 3 -> 7.95GB

-> nodetool repair, never ends (96 hours +), however there is no streams running, nor any
cpu or disk activity..

-> Manually killing the repair and restarting does not help.. Restarting the server/cassandra
does not help..

-> nodetool flush,compact,cleanup all complete, but do not help...

This is not occuring in 0.7.6.. I have come to the conclusion this is a Major 0.8 issue



Running: CentOS 5.6, JDK 1.6.0_26

  was:
I am seeing fatal problem in the new 0.8

Im running a 3 node cluster with a replication_factor of 3..

On Node 3.. If i 
# kill -9 cassandra-pid
# rm -rf "All data & logs"
# start cassandra
# nodetool -h "node-3-ip" repair

The whole cluster become duplicated..

* e.g Before 
node 1 -> 2.65GB
node 2 -> 2.65GB
node 3 -> 2.65GB

* e.g After
node 1 -> 5.3GB
node 2 -> 5.3GB
node 3 -> 7.95GB

-> nodetool repair, never ends (96 hours +), however there is no streams running, nor any
cpu or disk activity..

-> Manually killing the repair and restarting does not help.. Restarting the server/cassandra
does not help..

-> nodetool flush,compact,cleanup all complete, but do not help...

This is not occuring in 0.7.6.. I have come to the conclusion this is a Major 0.8 issue



Running: CentOS 5.6, JDK 1.6.0_26


> Repair Fails 0.8
> ----------------
>
>                 Key: CASSANDRA-2798
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2798
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: David Arena
>
> I am seeing a fatal problem in the new 0.8
> Im running a 3 node cluster with a replication_factor of 3..
> On Node 3.. If i 
> # kill -9 cassandra-pid
> # rm -rf "All data & logs"
> # start cassandra
> # nodetool -h "node-3-ip" repair
> The whole cluster become duplicated..
> * e.g Before 
> node 1 -> 2.65GB
> node 2 -> 2.65GB
> node 3 -> 2.65GB
> * e.g After
> node 1 -> 5.3GB
> node 2 -> 5.3GB
> node 3 -> 7.95GB
> -> nodetool repair, never ends (96 hours +), however there is no streams running,
nor any cpu or disk activity..
> -> Manually killing the repair and restarting does not help.. Restarting the server/cassandra
does not help..
> -> nodetool flush,compact,cleanup all complete, but do not help...
> This is not occuring in 0.7.6.. I have come to the conclusion this is a Major 0.8 issue
> Running: CentOS 5.6, JDK 1.6.0_26

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message