Thanks Ivo.
We are quite close to releasing so we'd hope to understand what causing the
error and may try to avoid it where possible. As said, it seems to work ok the
first time round.
The problem you referring in the last mail, was it restricted to bulk loading
or otherwise?
Thanks
-A
Iv
Hi all
First off, let's introduce the setup.
- 6 x C* 1.1.2 in active DC (DC1), another 6 in another (DC2)
- keyspace's RF=3 in each DC
- Hector as client.
- client talks only to DC1 unless DC1 can't serve the request. In which case
talks only to DC2
- commit log was periodically sync with the
Hi all
First off, please let me introduce the setup.
- a balance ring of 6 x C* 1.1.2 in active DC (DC1), 6 in another (DC2);
- keyspace's RF=3 in each DC;
- client talks only to DC1 unless DC1 can't serve the request, in which case
talks only to DC2;
- commit log is being sync periodicall
to verify
>
> Cheers
>
> -----
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 24/08/2012, at 6:01 AM, rubbish me wrote:
>
>> Hi all
>>
>> First off, let's introduce the setup.
>
oduce
> it with a single node ?
>
> Cheers
>
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 25/08/2012, at 11:00 AM, rubbish me wrote:
>
>> Thanks, Aaron, for your reply - please see the inline.
>>
>>
Hi all,
We have been using Cassandra for more than 3 years and now we have a cluster in
production still running on 1.1.x contains dynamic-columned column-families -
with hector as client.
We are trying to update to the latest 1.2.x and considering to use datastax
client in order to utilise
