That has GOT to be it. 1.1.10 upgrade it is...
On Wed, May 1, 2013 at 5:09 PM, Janne Jalkanen wrote:
>
> This sounds very much like
> https://issues.apache.org/jira/browse/CASSANDRA-5175, which was fixed in
> 1.1.10.
>
> /Janne
>
> On Apr 30, 2013, at 23:34 , aaron morton wrote:
>
> Many many
This sounds very much like
https://issues.apache.org/jira/browse/CASSANDRA-5175, which was fixed in 1.1.10.
/Janne
On Apr 30, 2013, at 23:34 , aaron morton wrote:
>> Many many many of the threads are trying to talk to IPs that aren't in the
>> cluster (I assume they are the IP's of dead hos
sstableloader directly streams sstables to the correct replica nodes. It
doesn't go through the normal coordinated write process, so consistency
levels do not apply.
On Wed, May 1, 2013 at 3:42 AM, Chandana Tummala wrote:
> Hi All,
>
> Hi All,
>
> We have a requirement to load approximately 10
I've done some more digging, and I have more data but no answers (not
knowing the cassandra internals).
Based on Aaron's comment about gossipinfo/thread dump:
-All IPs that gossip knows about have 2 threads in my thread dump (that
seems ok/fine)
-I have an additional set of IPs in my thread dump
Can I run scrub while the node is in the ring and receiving writes?
Or I should disable thrift before?
On 1 May 2013 15:52, wrote:
> Sounds like a job for “nodetool scrub”, which rewrites the SStable rows in
> the correct order. After the scrub, nodetool repair should succeed.
>
> ** **
>
>
Sounds like a job for "nodetool scrub", which rewrites the SStable rows in the
correct order. After the scrub, nodetool repair should succeed.
From: Haithem Jarraya [mailto:haithem.jarr...@struq.com]
Sent: Wednesday, May 01, 2013 5:46 PM
To: user@cassandra.apache.org
Subject: Repair session faile
Hi,
I am seeing this error message during repair,
INFO [AntiEntropyStage:1] 2013-05-01 14:30:54,300 AntiEntropyService.java
(line 764) [repair #ed104480-b26a-11e2-af9b-05179fa66b76] mycolumnfamily is
fully synced (1 remaining column family to sync for this session)
ERROR [Thread-12725] 2013-05-0
Hi John,
> - Each machine needed enough free diskspace to potentially hold the
entire cluster's sstables on disk
I wrote a possible explanation for why Cassandra is trying to use too much
space on your ticket:
https://issues.apache.org/jira/browse/CASSANDRA-5525
if you could provide the informa
