i am on DSE, and i am referring to the json manifest ... but my memory
isn't very good so i could have the name wrong. we are hitting this bug:
https://issues.apache.org/jira/browse/CASSANDRA-3306
On Wed, Dec 19, 2012 at 8:17 AM, Andras Szerdahelyi <
andras.szerdahe...@ignitionone.com> wrote:
Solr? Are you on DSE or am i missing something ( huge ) about Cassandra? (
wouldnt be the first time :-)
Or do you mean the json manifest ? Its there and it looks ok, in fact its been
corrupted twice due to storage problems and i hit
https://issues.apache.org/jira/browse/CASSANDRA-5041
TBH i t
in your data directory, for each keyspace there is a solr.json. cassandra
stores the SSTABLEs it knows about when using leveled compaction. take a
look at that file and see if it looks accurate. if not, this is a bug with
cassandra that we are checking into as well
On Thu, Dec 6, 2012 at 7:38
The log message matches what I would expect to see for nodetool -pr
Not using pr means repair all the ranges the node is a replica for. If you have
RF == number of nodes, then it will repair all the data.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
New Zealand
@aaronmo
Thanks!
i'm also thinking a repair run without -pr could have caused this maybe ?
Andras Szerdahelyi
Solutions Architect, IgnitionOne | 1831 Diegem E.Mommaertslaan 20A
M: +32 493 05 50 88 | Skype: sandrew84
[cid:7BDF7228-D831-4D98-967A-BE04FEB17544]
On 06 Dec 2012, at 04:05, aaron morton
> - how do i stop repair before i run out of storage? ( can't let this finish )
To stop the validation part of the repair…
nodetool -h localhost stop VALIDATION
The only way I know to stop streaming is restart the node, their may be a
better way though.
> INFO [AntiEntropySessions:3] 2012-
hi list,
AntiEntropyService started syncing ranges of entire nodes ( ?! ) across my data
centers and i'd like to understand why.
I see log lines like this on all my nodes in my two ( east/west ) data
centres...
INFO [AntiEntropySessions:3] 2012-12-05 02:15:02,301 AntiEntropyService.java
(line
Try a restart on that guy with and with the JVM option
-dcassandra.load_ring_state=false (see cassandra-env.sh).
If that does not fix it….
http://www.datastax.com/docs/0.8/troubleshooting/index#view-of-ring-differs-between-some-nodes
Cheers
-
Aaron Morton
Freelance Cassandra
All,
One node in my cluster returns a different answer for nodetool ring. It
seems to be ignorant of one of the other nodes. I've verified that all nodes
can ping each other without difficulty.
Here is the proper response:
Address DC RackStatus State LoadO
