We have upgraded our cassandra version to 2.0.7 and problem has been solved.
Thanks Russ,
On Wed, Apr 16, 2014 at 6:46 PM, Russell Hatch wrote:
> I think you might be seeing the issue reported in
> https://issues.apache.org/jira/browse/CASSANDRA-6971
>
> If that's the case, it looks like a fix
I think you might be seeing the issue reported in
https://issues.apache.org/jira/browse/CASSANDRA-6971
If that's the case, it looks like a fix will be in 2.0.7
Thanks,
Russ
On Tue, Apr 15, 2014 at 11:48 PM, Umut Kocasaraç wrote:
> Hi Olek,
>
> Could you solve the problem. Because we are exper
Hi Olek,
Could you solve the problem. Because we are experiencing exactly same
issue. We have 4 nodes and all of them are in different schema. Our
cassandra version is 2.0.6.
Umut
On Fri, Mar 21, 2014 at 12:26 AM, Robert Coli wrote:
> On Thu, Mar 20, 2014 at 2:23 PM, olek.stas...@gmail.com <
On Thu, Mar 20, 2014 at 2:23 PM, olek.stas...@gmail.com <
olek.stas...@gmail.com> wrote:
> Bump one more time, could anybody help me?
>
Unfortunately, while I can advise you how to resolve "my cluster has
multiple schema versions", I have no assistance to offer for "my cluster
ends up with split
Bump one more time, could anybody help me?
regards
Olek
2014-03-19 16:44 GMT+01:00 olek.stas...@gmail.com :
> Bump, could anyone comment this behaviour, is it correct, or should I
> create Jira task for this problems?
> regards
> Olek
>
> 2014-03-18 16:49 GMT+01:00 olek.stas...@gmail.com :
>> Oh,
Bump, could anyone comment this behaviour, is it correct, or should I
create Jira task for this problems?
regards
Olek
2014-03-18 16:49 GMT+01:00 olek.stas...@gmail.com :
> Oh, one more question: what should be configuration for storing
> system_traces keyspace? Should it be replicated or stored l
Oh, one more question: what should be configuration for storing
system_traces keyspace? Should it be replicated or stored locally?
Regards
Olek
2014-03-18 16:47 GMT+01:00 olek.stas...@gmail.com :
> Ok, i've dropped all system keyspaces, rebuild cluster and recover
> schema, now everything looks ok
Ok, i've dropped all system keyspaces, rebuild cluster and recover
schema, now everything looks ok.
But main goal of operations was to add new datacenter to cluster.
After starting node in new cluster two schema versions appear, one
version is held by 6 nodes of first datacenter, second one is in n
Ok, I'll do this during the weekend, I'll give you a feedback on Monday.
Regards
Aleksander
14 mar 2014 18:15 "Robert Coli" napisał(a):
> On Fri, Mar 14, 2014 at 12:40 AM, olek.stas...@gmail.com <
> olek.stas...@gmail.com> wrote:
>
>> OK, I see, so the data files stay in place, i have to just sto
On Fri, Mar 14, 2014 at 12:40 AM, olek.stas...@gmail.com <
olek.stas...@gmail.com> wrote:
> OK, I see, so the data files stay in place, i have to just stop
> cassandra on whole cluster, remove system schema and then start
> cluster and recreate all keyspaces with all column families? Data will
> b
OK, I see, so the data files stay in place, i have to just stop
cassandra on whole cluster, remove system schema and then start
cluster and recreate all keyspaces with all column families? Data will
be than loaded automatically from existing ssstables, right?
So one more question: what about KS sys
On Thu, Mar 13, 2014 at 1:20 PM, olek.stas...@gmail.com <
olek.stas...@gmail.com> wrote:
> Huh,
> you mean json dump?
>
If you're using cassandra-cli, I mean the output of "show schema;"
If you're using CQLsh, there is an analogous way to show all schema.
1) dump schema to a file via one of the
Huh,
you mean json dump?
Regards
Aleksander
2014-03-13 18:59 GMT+01:00 Robert Coli :
> On Thu, Mar 13, 2014 at 2:05 AM, olek.stas...@gmail.com
> wrote:
>>
>> Bump, are there any solutions to bring my cluster back to schema
>> consistency?
>> I've 6 node cluster with exactly six versions of schema
On Thu, Mar 13, 2014 at 2:05 AM, olek.stas...@gmail.com <
olek.stas...@gmail.com> wrote:
> Bump, are there any solutions to bring my cluster back to schema
> consistency?
> I've 6 node cluster with exactly six versions of schema, how to deal with
> it?
>
The simplest way, which is most likely to
Bump, are there any solutions to bring my cluster back to schema consistency?
I've 6 node cluster with exactly six versions of schema, how to deal with it?
regards
Aleksander
2014-03-11 14:36 GMT+01:00 olek.stas...@gmail.com :
> Didn't help :)
> thanks and regards
> Aleksander
>
> 2014-03-11 14:14
Didn't help :)
thanks and regards
Aleksander
2014-03-11 14:14 GMT+01:00 Duncan Sands :
> On 11/03/14 14:00, olek.stas...@gmail.com wrote:
>>
>> I plan to install 2.0.6 as soon as it will be available in datastax rpm
>> repo.
>> But how to deal with schema inconsistency on such scale?
>
>
> Does it
On 11/03/14 14:00, olek.stas...@gmail.com wrote:
I plan to install 2.0.6 as soon as it will be available in datastax rpm repo.
But how to deal with schema inconsistency on such scale?
Does it get better if you restart all the nodes? In my case restarting just
some of the nodes didn't help, bu
I plan to install 2.0.6 as soon as it will be available in datastax rpm repo.
But how to deal with schema inconsistency on such scale?
best regards
Aleksander
2014-03-11 13:40 GMT+01:00 Duncan Sands :
> Hi Aleksander, this may be related to CASSANDRA-6799 and CASSANDRA-6700 (if
> it is caused by C
Hi Aleksander, this may be related to CASSANDRA-6799 and CASSANDRA-6700 (if it
is caused by CASSANDRA-6700 then you are in luck: it is fixed in 2.0.6).
Best wishes, Duncan.
On 11/03/14 13:30, olek.stas...@gmail.com wrote:
Hi All,
I've faced an issue with cassandra 2.0.5.
I've 6 node cluster wi
Hi All,
I've faced an issue with cassandra 2.0.5.
I've 6 node cluster with random partitioner, still using tokens
instead of vnodes.
Cause we're changing hardware we decide to migrate cluster to 6 new
machines and change partitioning options to vnode rather then
token-based.
I've followed instructi
20 matches
Mail list logo
