incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sasha Dolgy <sdo...@gmail.com>
Subject Re: odd logs after repair
Date Tue, 14 Jun 2011 07:55:27 GMT
Hi ...

Does anyone else see these type of INFO messages in their log files,
or is i just me..?

INFO [manual-repair-1c6b33bc-ef14-4ec8-94f6-f1464ec8bdec] 2011-06-13
21:28:39,877 AntiEntropyService.java (line 177) Excluding
/10.128.34.18 from repair because it is on version 0.7 or sooner. You
should consider updating this node before running repair again.
ERROR [manual-repair-1c6b33bc-ef14-4ec8-94f6-f1464ec8bdec] 2011-06-13
21:28:39,877 AbstractCassandraDaemon.java (line 113) Fatal exception
in thread Thread[manual-repair-1c6b33bc-ef14-4ec8-94f6-f1464ec8bdec,5,RMI
Runtime]
java.util.ConcurrentModificationException
       at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
       at java.util.HashMap$KeyIterator.next(HashMap.java:828)
       at org.apache.cassandra.service.AntiEntropyService.getNeighbors(AntiEntropyService.java:173)
       at org.apache.cassandra.service.AntiEntropyService$RepairSession.run(AntiEntropyService.java:776)

I'm at a loss as to why this is showing up in the logs.
-sd

On Mon, Jun 13, 2011 at 3:58 PM, Sasha Dolgy <sdolgy@gmail.com> wrote:
> hm.  that's not it.  we've been using a non-standard jmx port for some time....
>
> i've dropped the keyspace and recreated ...
>
> wonder if that'll help
>
> On Mon, Jun 13, 2011 at 3:57 PM, Tyler Hobbs <tyler@datastax.com> wrote:
>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sdolgy@gmail.com> wrote:
>>>
>>> I recall there being a discussion about a default port changing from
>>> 0.7.x to 0.8.x ...this was JMX, correct?  Or were there others.
>>
>> Yes, the default JMX port changed from 8080 to 7199.  I don't think there
>> were any others.

Mime
View raw message