On Tue, May 7, 2013 at 4:26 AM, Philippe wrote :
> Definitely knew that for major releases, didn't expect it for a minor
> release at all.
This sort of incompatibility is definitely more common between major
versions, but not unheard of within minor series.
=Rob
Definitely knew that for major releases, didn't expect it for a minor
release at all.
Le 6 mai 2013 19:22, "Robert Coli" a écrit :
> On Sat, May 4, 2013 at 5:41 AM, Philippe wrote:
> > After trying every possible combination of parameters, config and the
> rest,
> > I ended up downgrading the ne
On Sat, May 4, 2013 at 5:41 AM, Philippe wrote:
> After trying every possible combination of parameters, config and the rest,
> I ended up downgrading the new node from 1.1.11 to 1.1.2 to match the
> existing 3 nodes. And that solved the issue immediately : the schema was
> propagated and the node
After trying every possible combination of parameters, config and the rest,
I ended up downgrading the new node from 1.1.11 to 1.1.2 to match the
existing 3 nodes. And that solved the issue immediately : the schema was
propagated and the node started handling reads & writes.
2013/5/3 Philippe
>
Unfortunately not, I've moved on to trying to add the nodes the current
cluster and then decommission the "old" ones.
But even that is not working, this is the strangest of things : while
trying to add a new node, I
- set its token to an existing value+1
- ensure the yaml (clutser name, partiti
> When I created the schema, the KS were created as directory in the .../data/
> directory
Can you provide the logs from start up ?
> I just noticed that when the new cluster nodes start up, auto_bootstrap is
> set to true. Given that it's no longer in the YAML file, I didn't set it to
> fals
Hi Aaron,
thanks for the response.
Permissions are correct : owner is cassandra (ubuntu) and permissions
are drwxr-xr-x
When I created the schema, the KS were created as directory in the
.../data/ directory
When I use cassandra-cli, set the CL to QUORUM, ensure two instances are up
(nodetool ring
Double check the file permissions ?
Write some data (using cqlsh or cassandra-cli) and flush to make sure the new
files are created where you expect them to be.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 1/05
Hello,
I'm trying to bring up a copy of an existing 3-node cluster running 1.0.8
into a 3-node cluster running 1.0.11.
The new cluster has been configured to have the same tokens and the same
partitioner.
Initially, I copied the files in the data directory of each node into their
corresponding no
