https://issues.apache.org/jira/browse/CASSANDRA-2768
On Tue, Jun 14, 2011 at 10:55 AM, Sylvain Lebresne wrote:
> Could you open a ticket then please ?
>
> --
> Sylvain
>
> On Tue, Jun 14, 2011 at 10:25 AM, Sasha Dolgy wrote:
>> Hi Sylvain,
>>
>> I verified on all nodes with nodetool version that
Could you open a ticket then please ?
--
Sylvain
On Tue, Jun 14, 2011 at 10:25 AM, Sasha Dolgy 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 no
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
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 b
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
shoul
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
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.
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 wrote:
> On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy wrote:
>>
>> I recall there being a discussion a
On Mon, Jun 13, 2011 at 8:41 AM, Sasha Dolgy 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 Hob
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 wrote:
> Hi Aaron,
>
> The error is being reported on all 4 nodes. I have confirmed (for my
> own sanity) that each nod
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-f146
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 ?
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
13 matches
Mail list logo
