No problem, glad to help. I'd love to see how it works out for you.
Clint
On Oct 5, 2015 8:12 AM, "Stephen Baynes"
wrote:
> Clint Martin's idea of each node creating its own keyspace, but then
> deciding which to use depending on the state of the cluster is really
> interesting. I am going to ex
Clint Martin's idea of each node creating its own keyspace, but then
deciding which to use depending on the state of the cluster is really
interesting. I am going to explore that in more detail.
Thanks for the good idea.
On 3 October 2015 at 00:03, Clint Martin <
clintlmar...@coolfiretechnologies
conflicts it will be
resolved on the basis of the row timestamp.
--
Jacques-Henri Berthemet
From: Stephen Baynes [mailto:stephen.bay...@smoothwall.net]
Sent: lundi 5 octobre 2015 11:00
To: user@cassandra.apache.org
Subject: Re: Changing schema on multiple nodes while they are isolated
> Why do
a automatically.
>
>
>
> *--*
>
> *Jacques-Henri Berthemet*
>
>
>
> *From:* Stephen Baynes [mailto:stephen.bay...@smoothwall.net]
> *Sent:* vendredi 2 octobre 2015 18:08
> *To:* user@cassandra.apache.org
> *Subject:* Re: Changing schema on multiple nodes while they are i
You could use a two key space method. At startup, wait some time for the
node to join the cluster.
the first time the app starts, you can be in one of three states:
The happiest state is that you succeed in joining a cluster. in this case
you will get replicated the cluster's keyspace and can s
On Fri, Oct 2, 2015 at 9:08 AM, Stephen Baynes <
stephen.bay...@smoothwall.net> wrote:
> Will need to do some thinking about this. I wonder about shiping a backup
> of a good system keyspace and restore it on each node before it starts for
> the first time - but will that end up with each node hav
multiple nodes while they are isolated
Hi Jacques-Henri
You are right - serious trouble. I managed some more testing and it does not
repair or share any data. In the logs I see lots of:
WARN [MessagingService-Incoming-/10.50.16.214<http://10.50.16.214>] 2015-10-02
16:52:
Hi Jacques-Henri
You are right - serious trouble. I managed some more testing and it does
not repair or share any data. In the logs I see lots of:
WARN [MessagingService-Incoming-/10.50.16.214] 2015-10-02 16:52:36,810
IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
soc
Hi Stephen,
If you manage to create tables on each node while node A and B are separated,
you’ll get into troubles when they will reconnect again. I had the case
previously and Cassandra complained that tables with same names but different
ids were present in the keyspace. I don’t know if there
