You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Emalayan Vairavanathan <sv...@yahoo.com> on 2013/05/23 02:31:08 UTC

Creating namespace and column family from multiple nodes concurrently

Hi all,

I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.

Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.

Please let me know if you have question.

Thank you
VE

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Faraaz Sareshwala <fs...@quantcast.com>.
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 time is schema
disagreement between cassandra instances. Read more about them and how to fix
them here:

http://wiki.apache.org/cassandra/FAQ#schema_disagreement

Is option 1 particularly difficult to do in your particular application?

Faraaz

On Wed, May 22, 2013 at 05:31:08PM -0700, Emalayan Vairavanathan wrote:
> Hi all,
> 
> I am implementing a distributed application which runs on 100s of machines
> concurrently. This application is going to use Cassandra as underlaying
> storage.
> 
> The application creates the schema (name space and column families) during
> initialization phase.  It seems I have two options to create the schema.
> 
> Option - 1 : Using a single node for schema creation.
>         Option - 2: Having all the nodes (> 100) to run the same schema
> creation logic (First, nodes will check whether the schema is already available
> and then try to create the schema if it is not available already).  
> 
> To keep the initialization phase simple, I prefer to go for Option - 2. However
> I am not sure how Cassandra is going to behave if multiple nodes try to create
> the same schema (namespace and column families) concurrently. It would be nice
> if someone can tell me about the implications of Option - 2 with Cassandra
> version 1.2.2.
> 
> Please let me know if you have question.
> 
> Thank you
> VE
> 
> 
> 
> 
>  

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Robert Coli <rc...@eventbrite.com>.
On Thu, May 23, 2013 at 12:07 PM, Emalayan Vairavanathan
<sv...@yahoo.com> 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 sure how Cassandra is going to behave if multiple nodes try
> to create the same schema (namespace and column families) concurrently. It
> would be nice if someone can tell me about the implications of Option - 2
> with Cassandra version 1.2.2.

Concurrent CREATE is allegedly working in 1.2.0, per NEWS.txt [1]. I
say allegedly working because this feature was also allegedly working
in 1.1.0. Given past experience, I continue to (perhaps
pessimistically) believe that frequent dynamic updates of schema are
likely to result in schema desynch. I would be interested to hear if
you go down this route and do not encounter problems.

See also CASSANDRA-3794 [2] for details.

=Rob

[1] https://github.com/apache/cassandra/blob/cassandra-1.2/NEWS.txt
[2] https://issues.apache.org/jira/browse/CASSANDRA-3794

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Arthur Zubarev <Ar...@Aol.com>.
Sorry for the belated reply.

Your approach #2 must work.

One concern I can think of: if the machines are spread across geographically and there is a substantial difference in network speed, AND you want to sync data this may take forever.
Also add a very good check on whether the schema got 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).

Let me put in another way... 

The application is composed of multiple instances of an executable. The application runs on multiple machines concurrently. All the instances are going to issue the same CQL command to and try to create exactly same namespace and column families.

Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan <sv...@yahoo.com>; user@cassandra.apache.org 
Sent: Thursday, 23 May 2013 1:15 PM
Subject: Re: Creating namespace and column family from 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 device/machine have its own keyspace?"

No. All the machines are going to run the exactly same CQL commands and going to create the same namespace and column families.

Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan <sv...@yahoo.com>; 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 any other verifications and it is going to be time consuming. 

From: Emalayan Vairavanathan 
Sent: Thursday, May 23, 2013 3:07 PM
To: user@cassandra.apache.org 
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 between the application initialization phase and the application runtime.  So as long as Cassandra can safely handle concurrent creation I should be fine.


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)? 
        - Does Cassandra take much time to agree on a final schema (In case if Cassandra is using some sort of exponential back off algorithms to handle schema conflicts) ? 
        - Or is it going to result schema conflicts which needs manual intervention ?
        - Or will this result in race conditions ?
        - Or some other issues e.g: memory/ cpu /network bottlenecks ?  


Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column family from multiple nodes concurrently


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 Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 pm
Subject: Creating namespace and column family from multiple nodes concurrently


Hi all,

I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.


Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.


Please let me know if you have question.


Thank you
VE





 










Re: Creating namespace and column family from multiple nodes concurrently

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
I am sorry if I was not clear. I was using nodes to refer machines (or vice versa).

Let me put in another way... 

The application is composed of multiple instances of an executable. The application runs on multiple machines concurrently. All the instances are going to issue the same CQL command to and try to create exactly same namespace and column families.

Thank you
Emalayan


________________________________
 From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan <sv...@yahoo.com>; user@cassandra.apache.org 
Sent: Thursday, 23 May 2013 1:15 PM
Subject: Re: Creating namespace and column family from 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 device/machine have its own keyspace?"
 
No. 
All the machines are going to run the exactly same CQL commands and going to 
create the same namespace and column families.
 
Thank 
you
Emalayan
 

________________________________
 From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan 
<sv...@yahoo.com>; 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 any other verifications and it is going to be time consuming.  
From: Emalayan Vairavanathan 
Sent: Thursday, May 23, 2013 3:07 PM
To: user@cassandra.apache.org 
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 thisis why I am preferring Option - 2. Further in my application, I have 
reasonable window between the application initialization phase and the 
application runtime.  So as long as Cassandra can safely handle concurrent 
creation I should be fine.

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)? 
        
- Does Cassandra take much time to agree on a final schema (In case if Cassandra 
is using some sort of exponential back off algorithms to handle schema 
conflicts) ? 
        
- Or is it going to result schema conflicts which needs manual intervention 
?
        
- Or will this result in race conditions ?
        
- Or some other issues e.g: memory/ cpu /network bottlenecks ?  

Thank you
Emalayan
 

________________________________
 From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; 
svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column 
family from multiple nodes concurrently

 
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 
Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: 
user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 
pm
Subject: Creating namespace and column family from multiple nodes 
concurrently


Hi all,
 
I 
am implementing a distributed application which runs on 100s of machines 
concurrently. This application is going to use Cassandra as underlaying 
storage.
 
The 
application creates the schema 
(name space and column families) during initialization phase.  It seems I have two options 
to create the schema.

Option - 1 : 
Using a single node for schema creation.
        
Option - 2: Having all the nodes (> 100) to run the same schema creation 
logic (First, nodes will check whether the schema is already available and then 
try to create the schema if it is not available already).  
 
To 
keep the initialization phase simple, I prefer to go for Option - 2. However I 
am not sure how Cassandra is going to behave if multiple nodes try to create the 
same schema (namespace and column families) concurrently. It would be nice if 
someone can tell me about the implications of Option - 2 with Cassandra version 
1.2.2.

Please let me know if you have 
question.

Thank you
VE

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Arthur Zubarev <Ar...@Aol.com>.
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 its own keyspace?"

No. All the machines are going to run the exactly same CQL commands and going to create the same namespace and column families.

Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan <sv...@yahoo.com>; 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 any other verifications and it is going to be time consuming. 

From: Emalayan Vairavanathan 
Sent: Thursday, May 23, 2013 3:07 PM
To: user@cassandra.apache.org 
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 between the application initialization phase and the application runtime.  So as long as Cassandra can safely handle concurrent creation I should be fine.


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)? 
        - Does Cassandra take much time to agree on a final schema (In case if Cassandra is using some sort of exponential back off algorithms to handle schema conflicts) ? 
        - Or is it going to result schema conflicts which needs manual intervention ?
        - Or will this result in race conditions ?
        - Or some other issues e.g: memory/ cpu /network bottlenecks ?  


Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column family from multiple nodes concurrently


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 Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 pm
Subject: Creating namespace and column family from multiple nodes concurrently


Hi all,

I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.


Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.


Please let me know if you have question.


Thank you
VE





 







Re: Creating namespace and column family from multiple nodes concurrently

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
"Would each device/machine have its own keyspace?"

No. All the machines are going to run the exactly same CQL commands and going to create the same namespace and column families.

Thank you
Emalayan


________________________________
 From: Arthur Zubarev <Ar...@Aol.com>
To: Emalayan Vairavanathan <sv...@yahoo.com>; 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 any other verifications and it is going to be time consuming.  
From: Emalayan Vairavanathan 
Sent: Thursday, May 23, 2013 3:07 PM
To: user@cassandra.apache.org 
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 thisis why I am preferring Option - 2. Further in my application, I have 
reasonable window between the application initialization phase and the 
application runtime.  So as long as Cassandra can safely handle concurrent 
creation I should be fine.

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)? 
        
- Does Cassandra take much time to agree on a final schema (In case if Cassandra 
is using some sort of exponential back off algorithms to handle schema 
conflicts) ? 
        
- Or is it going to result schema conflicts which needs manual intervention 
?
        
- Or will this result in race conditions ?
        
- Or some other issues e.g: memory/ cpu /network bottlenecks ?  

Thank you
Emalayan
 

________________________________
 From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; 
svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column 
family from multiple nodes concurrently

 
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 
Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: 
user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 
pm
Subject: Creating namespace and column family from multiple nodes 
concurrently


Hi all,
 
I 
am implementing a distributed application which runs on 100s of machines 
concurrently. This application is going to use Cassandra as underlaying 
storage.
 
The 
application creates the schema 
(name space and column families) during initialization phase.  It seems I have two options 
to create the schema.

Option - 1 : 
Using a single node for schema creation.
        
Option - 2: Having all the nodes (> 100) to run the same schema creation 
logic (First, nodes will check whether the schema is already available and then 
try to create the schema if it is not available already).  
 
To 
keep the initialization phase simple, I prefer to go for Option - 2. However I 
am not sure how Cassandra is going to behave if multiple nodes try to create the 
same schema (namespace and column families) concurrently. It would be nice if 
someone can tell me about the implications of Option - 2 with Cassandra version 
1.2.2.

Please let me know if you have 
question.

Thank you
VE

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Arthur Zubarev <Ar...@Aol.com>.
Would each device/machine have its own keyspace?

Basically, your client needs to take care of a successful creation of the schema and any other verifications and it is going to be time consuming. 

From: Emalayan Vairavanathan 
Sent: Thursday, May 23, 2013 3:07 PM
To: user@cassandra.apache.org 
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 between the application initialization phase and the application runtime.  So as long as Cassandra can safely handle concurrent creation I should be fine.


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)? 
        - Does Cassandra take much time to agree on a final schema (In case if Cassandra is using some sort of exponential back off algorithms to handle schema conflicts) ? 
        - Or is it going to result schema conflicts which needs manual intervention ?
        - Or will this result in race conditions ?
        - Or some other issues e.g: memory/ cpu /network bottlenecks ?  


Thank you
Emalayan


--------------------------------------------------------------------------------
From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column family from multiple nodes concurrently


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 Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 pm
Subject: Creating namespace and column family from multiple nodes concurrently


Hi all,

I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.


Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.


Please let me know if you have question.


Thank you
VE





 




Re: Creating namespace and column family from multiple nodes concurrently

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
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 between the application initialization phase and the application runtime.  So as long as Cassandra can safely handle concurrent creation I should be fine.

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)? 
        - Does Cassandra take much time to agree on a final schema (In case if Cassandra is using some sort of exponential back off algorithms to handle schema conflicts) ? 
        - Or is it going to result schema conflicts which needs manual intervention ?
        - Or will this result in race conditions ?
        - Or some other issues e.g: memory/ cpu /network bottlenecks ?  

Thank you
Emalayan


________________________________
 From: Arthur Zubarev <ar...@aol.com>
To: user@cassandra.apache.org; svemalayan@yahoo.com 
Sent: Wednesday, 22 May 2013 8:07 PM
Subject: Re: Creating namespace and column family from multiple nodes concurrently
 


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 Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 pm
Subject: Creating namespace and column family from multiple nodes concurrently


Hi all,

I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.

Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.

Please let me know if you have question.

Thank you
VE

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Arthur Zubarev <ar...@aol.com>.
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 Message-----
From: Emalayan Vairavanathan <sv...@yahoo.com>
To: user <us...@cassandra.apache.org>
Sent: Wed, May 22, 2013 8:31 pm
Subject: Creating namespace and column family from multiple nodes concurrently



Hi all,


I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.


The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.


	Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  


To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.


Please let me know if you have question.


Thank you
VE








 


 

Re: Cassandra 2.0 new features ?

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
Great. Thank you Tomaz.


________________________________
 From: Tomaz Muraus <to...@apache.org>
To: dev@cassandra.apache.org; Emalayan Vairavanathan <sv...@yahoo.com> 
Sent: Wednesday, 12 June 2013 4:39 PM
Subject: Re: Cassandra 2.0 new features ?
 


Check CHANGES file (https://github.com/apache/cassandra/blob/trunk/CHANGES.txt) and / or JIRA (https://issues.apache.org/jira/browse/CASSANDRA).


On Wed, Jun 12, 2013 at 3:48 PM, Emalayan Vairavanathan <sv...@yahoo.com> wrote:

Hi All,
>
>Can anyone tell me about the new features that are going to come in Cassandra 2.0 ?
>
>Thank you
>Emalayan

Re: Cassandra 2.0 new features ?

Posted by Tomaz Muraus <to...@apache.org>.
Check CHANGES file (
https://github.com/apache/cassandra/blob/trunk/CHANGES.txt) and / or JIRA (
https://issues.apache.org/jira/browse/CASSANDRA).

On Wed, Jun 12, 2013 at 3:48 PM, Emalayan Vairavanathan <
svemalayan@yahoo.com> wrote:

> Hi All,
>
> Can anyone tell me about the new features that are going to come in
> Cassandra 2.0 ?
>
> Thank you
> Emalayan

Cassandra 2.0 new features ?

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
Hi All,

Can anyone tell me about the new features that are going to come in Cassandra 2.0 ?

Thank you
Emalayan

Re: Creating namespace and column family from multiple nodes concurrently

Posted by Michael Kjellman <mk...@barracuda.com>.
You will most likely get better answers to your if you try the Cassandra
users group instead for your question.

Best,
Michael

On 5/22/13 5:52 PM, "Emalayan Vairavanathan" <sv...@yahoo.com> wrote:

>Hi all,
>
>
>
>I am implementing a distributed application which runs on 100s of
>machines concurrently. This application is going to use Cassandra as
>underlaying storage.
>
>The application creates the schema (name space and column families)
>during initialization phase.  It seems I have two options to create the
>schema.
>
>Option - 1 : Using a single node for schema creation.
>        Option - 2: Having all the nodes (> 100) to run the same schema
>creation logic (First, nodes will check whether the schema is already
>available and then try to create the schema if it is not available
>already).  
>
>To keep the initialization phase simple, I prefer to go for Option - 2.
>However I am not sure how Cassandra is going to behave if multiple nodes
>try to create the same schema (namespace and column families)
>concurrently. It would be nice if someone can tell me about the
>implications of Option - 2 with Cassandra version 1.2.2.
>
>Please let me know if you have question.
>
>Thank you
>VE


Creating namespace and column family from multiple nodes concurrently

Posted by Emalayan Vairavanathan <sv...@yahoo.com>.
Hi all,



I am implementing a distributed application which runs on 100s of machines concurrently. This application is going to use Cassandra as underlaying storage.

The application creates the schema (name space and column families) during initialization phase.  It seems I have two options to create the schema.

Option - 1 : Using a single node for schema creation.
        Option - 2: Having all the nodes (> 100) to run the same schema creation logic (First, nodes will check whether the schema is already available and then try to create the schema if it is not available already).  

To keep the initialization phase simple, I prefer to go for Option - 2. However I am not sure how Cassandra is going to behave if multiple nodes try to create the same schema (namespace and column families) concurrently. It would be nice if someone can tell me about the implications of Option - 2 with Cassandra version 1.2.2.

Please let me know if you have question.

Thank you
VE