applied.
Good Luck!
From: Emalayan Vairavanathan
Sent: Friday, May 24, 2013 1:14 AM
To: user@cassandra.apache.org ; Arthur Zubarev
Subject: Re: Creating namespace and column family from multiple nodes
concurrently
I am sorry if I was not clear. I was using nodes to refer machines (or vice
versa
multiple nodes
concurrently
so where the multiple nodes are? I am just puzzled
From: Emalayan Vairavanathan
Sent: Thursday, May 23, 2013 3:43 PM
To: Arthur Zubarev ; user@cassandra.apache.org
Subject: Re: Creating namespace and column family from multiple
nodes concurrently
"Would
each d
so where the multiple nodes are? I am just puzzled
From: Emalayan Vairavanathan
Sent: Thursday, May 23, 2013 3:43 PM
To: Arthur Zubarev ; user@cassandra.apache.org
Subject: Re: Creating namespace and column family from multiple nodes
concurrently
"Would each device/machine have it
On Thu, May 23, 2013 at 12:07 PM, Emalayan Vairavanathan
wrote:
> Do you have any idea how Cassandra is going to handle concurrent namespace
> and column family creation (Here all the instances are going to create the
> same namespace and column families concurrently)?
> [...]
> However I am not s
han ; user@cassandra.apache.org
Sent: Thursday, 23 May 2013 12:20 PM
Subject: Re: Creating namespace and column family from multiple nodes
concurrently
Would each device/machine have its own keyspace?
Basically, your client needs to take care of a successful creation of the
schema and
Subject: Re: Creating namespace and column family from multiple nodes
concurrently
Hi Arthur and Farraz,
Thank you for getting back to me.
I am trying to avoid sync among concurrent instances and this is why I am
preferring Option - 2. Further in my application, I have reasonable window
some other issues e.g: memory/ cpu /network bottlenecks ?
Thank you
Emalayan
From: Arthur Zubarev
To: user@cassandra.apache.org; svemala...@yahoo.com
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column family from multiple nodes
I am assuming here you want to sync all the 100s of nodes once the application
is airborne. I suspect this would flood the network and even potentially affect
the machine itself memory-wise. How are you going to maintain the nodes
(compaction+repair)?
Regards,
Arthur
-Original
Others on this list may know better, but it might not be good to have all your
clients create a schema on initialization. They can all use it once it has been
created, but creating it should be done by a single entity. One of the issues
that can come up if you make changes to schemas at the same ti
