<mailto:user@cassandra.apache.org>>
> Date: Thursday, March 14, 2013 8:09 AM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: Failed migration from 1.1.6 to 1.2.2
>From output.log with debug enable i have more information.
...
DEBUG 15:29:58,885 collecting 0 of 2147483647:
users:bloom_filter_fp_chance:false:8@1363254809666000
DEBUG 15:29:58,885 collecting 1 of 2147483647:
users:caching:false:9@1363254809666000
DEBUG 15:29:58,886 collecting 2 of 2147483647:
@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Failed migration from 1.1.6 to 1.2.2
@Dean
"It is expensive?"
I was talking about a full time QA environment equal or similar to a prod env.
I didn't thought about using a temp QA, and you are rig
"on my workstation with a < 0.01% sample of production"
Is there a simple way of getting that ?
On "Cassandra level"? Nope. I just had to prepare these data "manualy"
using software we develop on very small input. I understand that it
might not be so easy in all the use cases, as it was in
he.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Thursday, March 14, 2013 7:41 AM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cas
We have no such environment. It is expensive, we can't afford this for now.
We do have QA cluster, but before even trying the 1.1.0 -> 1.1.9 / 1.2.1
upgrade on it (we were a bit undecided about the version ;-) ), I did
some experiments using ccm ( https://github.com/pcmanus/ccm ) on my
workst
;
Date: Thursday, March 14, 2013 7:41 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Failed migration from 1.1.6 to 1.2.2
@Aaron
"You can try to reset the cluster ring state by doing a rolling restart
ursday, March 14, 2013 5:31 AM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: Failed migration from 1.1.6 to 1.2.2
>
> We have it set to 0.0.0.0 but anywa
ndra.apache.org>>
Date: Thursday, March 14, 2013 5:31 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Failed migration from 1.1.6 to 1.2.2
We have it set to 0.0.0.0 but anyway, as told before, I don&#x
> ERROR [RequestResponseStage:2] 2013-03-14 09:53:25,750
> AbstractCassandraDaemon.java (line 135) Exception in thread
> Thread[RequestResponseStage:2,5,main]
> java.io.IOError: java.io.EOFException
> at
> org.apache.cassandra.service.AbstractRowResolver.preprocess(AbstractRowResolver.ja
We have it set to 0.0.0.0 but anyway, as told before, I don't think our
problem come from this bug.
2013/3/14 Michal Michalski
>
> It will happen if your rpc_address is set to 0.0.0.0.
>>
>
> Ops, it's not what I meant ;-)
> It will happen, if your rpc_address is set to IP that is not defined
It will happen if your rpc_address is set to 0.0.0.0.
Ops, it's not what I meant ;-)
It will happen, if your rpc_address is set to IP that is not defined in
your cluster's config (e.g. in cassandra-topology.properties for
PropertyFileSnitch)
M.
M.
W dniu 14.03.2013 13:03, Alain RODRIGU
Well it seems I have nothing like this when I run a $grep "Unknown host"
/var/log/cassandra/system.log.
This issue was reported in 1.2.1 and commited to the trunk. It may have
been fixed in 1.2.2 even if I can't see the release version from the jira
nor can I see it in the changelog.
Thanks again
Just to make it clear: This bug will occur on single-DC configuration too.
In our case it resulted in Exception like this at the very end of node
startup:
ERROR [WRITE-/] 2013-02-27 12:14:55,433 CassandraDaemon.java
(line 133) Exception in thread Thread[WRITE-/,5,main]
java.lang.RuntimeExcep
Thanks for this pointer but I don't think this is the source of our problem
since we use 1 data center and Ec2Snitch.
2013/3/14 Jean-Armel Luce
> Hi Alain,
>
> Maybe it is due to https://issues.apache.org/jira/browse/CASSANDRA-5299
>
> A patch is provided with this ticket.
>
> Regards.
>
> Jea
Hi Alain,
Maybe it is due to https://issues.apache.org/jira/browse/CASSANDRA-5299
A patch is provided with this ticket.
Regards.
Jean Armel
2013/3/14 Alain RODRIGUEZ
> Hi
>
> We just tried to migrate our production cluster from C* 1.1.6 to 1.2.2.
>
> This has been a disaster. I just switch o
Hi
We just tried to migrate our production cluster from C* 1.1.6 to 1.2.2.
This has been a disaster. I just switch one node to 1.2.2, updated its
configuration (cassandra.yaml / cassandra-env.sh) and restart it.
It resulted on error on all the 5 remaining 1.1.6 nodes :
ERROR [RequestResponseSta
17 matches
Mail list logo
