You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Sasha Dolgy <sd...@gmail.com> on 2011/06/12 20:19:47 UTC
odd logs after repair
Hi Everyone,
Last week, upgraded all 4 nodes to apache-cassandra-0.8.0 .. no
issues. Trolling the logs today, I find messages like this on all
four nodes:
INFO [manual-repair-0b61c9e2-3593-4633-a80f-b6ca52cfe948] 2011-06-13
02:16:45,978 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.
Maybe it would be nice to have the version of all nodes print in
nodetool ring ? I don't think I'm crazy though ... have manually
checked all are on 0.8.0
--
Sasha Dolgy
sasha.dolgy@gmail.com
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
https://issues.apache.org/jira/browse/CASSANDRA-2768
On Tue, Jun 14, 2011 at 10:55 AM, Sylvain Lebresne <sy...@datastax.com> wrote:
> Could you open a ticket then please ?
>
> --
> Sylvain
>
> On Tue, Jun 14, 2011 at 10:25 AM, Sasha Dolgy <sd...@gmail.com> wrote:
>> Hi Sylvain,
>>
>> I verified on all nodes with nodetool version that they are 0.8 and have
>> even restarted nodes. Still persists. The four nodes all report similar
>> errors about the other nodes.
>>
>> When i upgraded to 0.8 maybe there were relics about the keyspace that say
>> it's from an earlier version?
>>
>> I need to create a new keyspace to see if that fixes the error....
>>
>> On Jun 14, 2011 10:08 AM, "Sylvain Lebresne" <sy...@datastax.com> wrote:
>>> The exception itself is a bug (I've created
>>> https://issues.apache.org/jira/browse/CASSANDRA-2767 to fix it).
>>>
>>> However, the important message is the previous one (Even if the
>>> exception was not thrown, repair wouldn't be able to work correctly,
>>> so the fact that the exception is thrown is not such a big deal).
>>> Apparently, from the standpoint of whomever node this logs is from,
>>> the node 10.128.34.18 is still running 0.7. You should check if it is
>>> the case (restarting 10.128.34.18 and look for something like
>>> 'Cassandra version: 0.8.0' is one solution). If the does does run
>>> 0.8.0 and you still get this error, then it would point to a problem
>>> with our detection of the nodes.
>>>
>>> --
>>> Sylvain
>>>
>>> On Tue, Jun 14, 2011 at 9:55 AM, Sasha Dolgy <sd...@gmail.com> wrote:
>>>> 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 <sd...@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 <ty...@datastax.com> wrote:
>>>>>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
>>>>
>>
>
--
Sasha Dolgy
sasha.dolgy@gmail.com
Re: odd logs after repair
Posted by Sylvain Lebresne <sy...@datastax.com>.
Could you open a ticket then please ?
--
Sylvain
On Tue, Jun 14, 2011 at 10:25 AM, Sasha Dolgy <sd...@gmail.com> wrote:
> Hi Sylvain,
>
> I verified on all nodes with nodetool version that they are 0.8 and have
> even restarted nodes. Still persists. The four nodes all report similar
> errors about the other nodes.
>
> When i upgraded to 0.8 maybe there were relics about the keyspace that say
> it's from an earlier version?
>
> I need to create a new keyspace to see if that fixes the error....
>
> On Jun 14, 2011 10:08 AM, "Sylvain Lebresne" <sy...@datastax.com> wrote:
>> The exception itself is a bug (I've created
>> https://issues.apache.org/jira/browse/CASSANDRA-2767 to fix it).
>>
>> However, the important message is the previous one (Even if the
>> exception was not thrown, repair wouldn't be able to work correctly,
>> so the fact that the exception is thrown is not such a big deal).
>> Apparently, from the standpoint of whomever node this logs is from,
>> the node 10.128.34.18 is still running 0.7. You should check if it is
>> the case (restarting 10.128.34.18 and look for something like
>> 'Cassandra version: 0.8.0' is one solution). If the does does run
>> 0.8.0 and you still get this error, then it would point to a problem
>> with our detection of the nodes.
>>
>> --
>> Sylvain
>>
>> On Tue, Jun 14, 2011 at 9:55 AM, Sasha Dolgy <sd...@gmail.com> wrote:
>>> 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 <sd...@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 <ty...@datastax.com> wrote:
>>>>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
>>>
>
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
Hi Sylvain,
I verified on all nodes with nodetool version that they are 0.8 and have
even restarted nodes. Still persists. The four nodes all report similar
errors about the other nodes.
When i upgraded to 0.8 maybe there were relics about the keyspace that say
it's from an earlier version?
I need to create a new keyspace to see if that fixes the error....
On Jun 14, 2011 10:08 AM, "Sylvain Lebresne" <sy...@datastax.com> wrote:
> The exception itself is a bug (I've created
> https://issues.apache.org/jira/browse/CASSANDRA-2767 to fix it).
>
> However, the important message is the previous one (Even if the
> exception was not thrown, repair wouldn't be able to work correctly,
> so the fact that the exception is thrown is not such a big deal).
> Apparently, from the standpoint of whomever node this logs is from,
> the node 10.128.34.18 is still running 0.7. You should check if it is
> the case (restarting 10.128.34.18 and look for something like
> 'Cassandra version: 0.8.0' is one solution). If the does does run
> 0.8.0 and you still get this error, then it would point to a problem
> with our detection of the nodes.
>
> --
> Sylvain
>
> On Tue, Jun 14, 2011 at 9:55 AM, Sasha Dolgy <sd...@gmail.com> wrote:
>> 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 <sd...@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 <ty...@datastax.com> wrote:
>>>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
>>
Re: odd logs after repair
Posted by Sylvain Lebresne <sy...@datastax.com>.
The exception itself is a bug (I've created
https://issues.apache.org/jira/browse/CASSANDRA-2767 to fix it).
However, the important message is the previous one (Even if the
exception was not thrown, repair wouldn't be able to work correctly,
so the fact that the exception is thrown is not such a big deal).
Apparently, from the standpoint of whomever node this logs is from,
the node 10.128.34.18 is still running 0.7. You should check if it is
the case (restarting 10.128.34.18 and look for something like
'Cassandra version: 0.8.0' is one solution). If the does does run
0.8.0 and you still get this error, then it would point to a problem
with our detection of the nodes.
--
Sylvain
On Tue, Jun 14, 2011 at 9:55 AM, Sasha Dolgy <sd...@gmail.com> wrote:
> 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 <sd...@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 <ty...@datastax.com> wrote:
>>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
>
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
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 <sd...@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 <ty...@datastax.com> wrote:
>> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
Re: odd logs after repair
Posted by aaron morton <aa...@thelastpickle.com>.
Count of the columns in a row, not an exact count as that would requiring stopping clients from writing to the row and we do not do that.
Have a poke around
http://www.datastax.com/docs/0.8/data_model/index
and
http://wiki.apache.org/cassandra/DataModel
Or are you asking about counter columns ?
Cheers
-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 14 Jun 2011, at 03:27, Sijie YANG wrote:
> Hi, All
>
> I am newbie to cassandra. I have a simple question but don't find any clear answer by searching google:
> What's the meaning of count column in Cassandra? Thanks.
Re: odd logs after repair
Posted by Sijie YANG <iy...@gmail.com>.
Hi, All
I am newbie to cassandra. I have a simple question but don't find any clear
answer by searching google:
What's the meaning of count column in Cassandra? Thanks.
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
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 <ty...@datastax.com> wrote:
> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
Re: odd logs after repair
Posted by Tyler Hobbs <ty...@datastax.com>.
On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy <sd...@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.
--
Tyler Hobbs
Software Engineer, DataStax <http://datastax.com/>
Maintainer of the pycassa <http://github.com/pycassa/pycassa> Cassandra
Python client library
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
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.
On Mon, Jun 13, 2011 at 3:34 PM, Sasha Dolgy <sd...@gmail.com> wrote:
> Hi Aaron,
>
> The error is being reported on all 4 nodes. I have confirmed (for my
> own sanity) that each node is running: ReleaseVersion: 0.8.0
>
> I can reproduce the error on any node by trailing
> cassandra/logs/system.log and running "nodetool repair"
>
> 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)
>
> When I run nodetool ring, the ring looks balanced and nothing out of sorts.
>
> I also have this set up with RF=3 on 4 nodes ... but repair was
> working fine prior to the 0.8.0 upgrade.
>
> Are there any special commands I need to run? I've tried scrub,
> cleanup, flush too ... still, repair gives the same issues.
>
> -- I have stopped one of the nodes and started it. Issue still
> persists. I stop another node that is reported in the logs (like .18
> above) and start it ... run repair again ... issue is persisted to the
> log file still.
>
> -sd
>
>
>
> On Mon, Jun 13, 2011 at 3:02 PM, aaron morton <aa...@thelastpickle.com> wrote:
>> You can double check with node tool e.g.
>>
>> $ ./bin/nodetool -h localhost version
>> ReleaseVersion: 0.8.0-SNAPSHOT
>>
>> This error is about the internode wire protocol one node thinks another is using. Not sure how it could get confused, does it go away if you restart the node that logged the error ?
>>
>> Cheers
>>
>> -----------------
>> Aaron Morton
>> Freelance Cassandra Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 13 Jun 2011, at 06:19, Sasha Dolgy wrote:
>>
>>> Hi Everyone,
>>>
>>> Last week, upgraded all 4 nodes to apache-cassandra-0.8.0 .. no
>>> issues. Trolling the logs today, I find messages like this on all
>>> four nodes:
>>>
>>> INFO [manual-repair-0b61c9e2-3593-4633-a80f-b6ca52cfe948] 2011-06-13
>>> 02:16:45,978 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.
>>>
>>> Maybe it would be nice to have the version of all nodes print in
>>> nodetool ring ? I don't think I'm crazy though ... have manually
>>> checked all are on 0.8.0
>>>
>>>
>>> --
>>> Sasha Dolgy
>>> sasha.dolgy@gmail.com
>>
>>
>
>
>
> --
> Sasha Dolgy
> sasha.dolgy@gmail.com
>
--
Sasha Dolgy
sasha.dolgy@gmail.com
Re: odd logs after repair
Posted by Sasha Dolgy <sd...@gmail.com>.
Hi Aaron,
The error is being reported on all 4 nodes. I have confirmed (for my
own sanity) that each node is running: ReleaseVersion: 0.8.0
I can reproduce the error on any node by trailing
cassandra/logs/system.log and running "nodetool repair"
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)
When I run nodetool ring, the ring looks balanced and nothing out of sorts.
I also have this set up with RF=3 on 4 nodes ... but repair was
working fine prior to the 0.8.0 upgrade.
Are there any special commands I need to run? I've tried scrub,
cleanup, flush too ... still, repair gives the same issues.
-- I have stopped one of the nodes and started it. Issue still
persists. I stop another node that is reported in the logs (like .18
above) and start it ... run repair again ... issue is persisted to the
log file still.
-sd
On Mon, Jun 13, 2011 at 3:02 PM, aaron morton <aa...@thelastpickle.com> wrote:
> You can double check with node tool e.g.
>
> $ ./bin/nodetool -h localhost version
> ReleaseVersion: 0.8.0-SNAPSHOT
>
> This error is about the internode wire protocol one node thinks another is using. Not sure how it could get confused, does it go away if you restart the node that logged the error ?
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 13 Jun 2011, at 06:19, Sasha Dolgy wrote:
>
>> Hi Everyone,
>>
>> Last week, upgraded all 4 nodes to apache-cassandra-0.8.0 .. no
>> issues. Trolling the logs today, I find messages like this on all
>> four nodes:
>>
>> INFO [manual-repair-0b61c9e2-3593-4633-a80f-b6ca52cfe948] 2011-06-13
>> 02:16:45,978 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.
>>
>> Maybe it would be nice to have the version of all nodes print in
>> nodetool ring ? I don't think I'm crazy though ... have manually
>> checked all are on 0.8.0
>>
>>
>> --
>> Sasha Dolgy
>> sasha.dolgy@gmail.com
>
>
--
Sasha Dolgy
sasha.dolgy@gmail.com
Re: odd logs after repair
Posted by aaron morton <aa...@thelastpickle.com>.
You can double check with node tool e.g.
$ ./bin/nodetool -h localhost version
ReleaseVersion: 0.8.0-SNAPSHOT
This error is about the internode wire protocol one node thinks another is using. Not sure how it could get confused, does it go away if you restart the node that logged the error ?
Cheers
-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 13 Jun 2011, at 06:19, Sasha Dolgy wrote:
> Hi Everyone,
>
> Last week, upgraded all 4 nodes to apache-cassandra-0.8.0 .. no
> issues. Trolling the logs today, I find messages like this on all
> four nodes:
>
> INFO [manual-repair-0b61c9e2-3593-4633-a80f-b6ca52cfe948] 2011-06-13
> 02:16:45,978 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.
>
> Maybe it would be nice to have the version of all nodes print in
> nodetool ring ? I don't think I'm crazy though ... have manually
> checked all are on 0.8.0
>
>
> --
> Sasha Dolgy
> sasha.dolgy@gmail.com