http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name Software, Support, and Training for Apache Cassandra en-US Mon, 20 May 2013 01:20:10 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-499 Fri, 09 Sep 2011 18:18:45 +0000 joaquin 499@http://www.datastax.com/support-forums/ <p>Also, just to make sure we are on the same page.</p> <p>The reason Brisk starts up with 2 DataCenters is to avoid your real-time datacenter getting bogged down by your analytics. But by using Cassandra's innate datacenter knowledge, you are also able to run analytics on real-time data without having to do a full move of data to a separate cluster.</p> <p>I'm assuming this is not the case with your cluster, but I wanted to make sure though.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-498 Fri, 09 Sep 2011 18:14:00 +0000 joaquin 498@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>You are correct. As of now you would have to use the Property File to make this work.</p> <p>It is in no way a hack and is actually the recommended way to bring up servers in production. This guarantees a more stable layout, one that you have provided. The EC2Snitch and BriskSnitch are convenience snitches, of sorts.</p> <p><a href="http://www.datastax.com/docs/0.8/operations/datacenter" rel="nofollow">http://www.datastax.com/docs/0.8/operations/datacenter</a></p> <p>The link above shows DC1 and DC2 being created. (Ignore the creation of racks, since you won't know this information from EC2.)</p> <p>Then for the strategy options you would change both brisk_system and cfs to from [Brisk:1, Cassandra:0] to [DC1: 1, DC2: 1] using these lines:</p> <p>update keyspace brisk_system with strategy_options = [{DC1:1, DC2:1}];<br /> update keyspace cfs with strategy_options = [{DC1:1, DC2:1}];</p> <p>Let me know if you still have issues or concerns.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-497 Fri, 09 Sep 2011 14:57:46 +0000 Anonymous 497@http://www.datastax.com/support-forums/ <p>Joaquin,</p> <p>I'm confused here. How could I use the NetworkTopologyProperties without using the Property File snitch or am I missing something. Could you possibly provide a sample keyspace update statement? I would imaging this is a question many people would have who are changing to Brisk. </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-494 Thu, 08 Sep 2011 23:36:10 +0000 joaquin 494@http://www.datastax.com/support-forums/ <p>I'm sorry, Jackson has brought the internal workings of the EC2Snitch to my attention. I thought availability zones mapped to datacenters, but it turns out regions:azs map to dcs:racks.</p> <p>Sorry for the confusion.</p> <p>So what you would need to do is use the NetworkTopologyProperties to set the availability zones to map to Datacenters. Once that happens, then you would be able to follow the rest of what I had posted. </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-493 Thu, 08 Sep 2011 18:37:23 +0000 joaquin 493@http://www.datastax.com/support-forums/ <p>The way that racks normally work is like this:<br /> <a href="http://www.datastax.com/docs/0.8/operations/datacenter" rel="nofollow">http://www.datastax.com/docs/0.8/operations/datacenter</a></p> <p>What I was suggesting was leaving everything as is for the EC2Snitch, but when you see a Strategy option of ['Brisk':1, 'Cassandra': 0], change this to ['az1': 1, 'az2':1, Cassandra:'0'], for the names that show up naturally with the EC2Snitch, since this has currently slipped my mind. Using this form of replication, will ensure that the data is available in each of the availability zones.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-492 Thu, 08 Sep 2011 12:23:41 +0000 Anonymous 492@http://www.datastax.com/support-forums/ <p>Does that mean that Brisk natively looks at the "rack" name for replication placement? </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-491 Wed, 07 Sep 2011 18:41:31 +0000 joaquin 491@http://www.datastax.com/support-forums/ <p>With regarding Brisk, the BriskSimpleSnitch uses DataCenter name "Brisk" and "Cassandra", and Rack name as "rack1". Basically if a Cassandra node is running with a task tracker, then the DataCenter that this node belongs to would be noted as "Brisk", otherwise it would be "Cassandra".</p> <p>What you can do is change the strategy_options to use the EC2Snitch names. To do so, access the cassandra-cli, and update the keyspace strategy_options to not use Brisk and Cassandra and instead use the EC2Snitch names.</p> <p>Due keep <a href="https://issues.apache.org/jira/browse/CASSANDRA-3114" rel="nofollow">https://issues.apache.org/jira/browse/CASSANDRA-3114</a> in mind since you may hit this bug during your changes.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-490 Wed, 07 Sep 2011 14:33:45 +0000 Anonymous 490@http://www.datastax.com/support-forums/ <p>We are deploying all nodes as Brisk nodes (with hadoop enabled). How would I go about using propertyfile snitch without making the system blow up?</p> <p>Does the datacenter name have to be "Brisk"? </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-489 Tue, 06 Sep 2011 17:45:14 +0000 joaquin 489@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>If you were to start up nodes in availability zone 1 with the task tracker enabled, and others in availability zone 2 as just vanilla Cassandra, then Brisk would be able to find itself without issue, split into two datacenters, and you ensure that each part of the ring is in different availability zones.</p> <p>You could also setup the propertyfile snitch, and keep them the same on all machines, which would be the most robust way to manage such a cluster.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/ec2snitchpropertyfile-snitches-brisk-datacenter-name#post-488 Tue, 06 Sep 2011 13:18:36 +0000 Anonymous 488@http://www.datastax.com/support-forums/ <p>Hi all,</p> <p>I am setting up Brisk on EC2 in a multi-az setup. I had used the ec2snitch with Apache Cassandra but we need the capabilities Brisk provides. From what I can tell, Brisk uses very custom datacenter names to ensure replication factors. I did try setting up the ec2snitch in the cassandra.yaml file and the system immediately halted and I had to revert to the BriskSimpleSnitch.</p> <p>So here is my problem.</p> <p>I need to ensure the data is in two datacenters. I have puppet running so I could derive a custom fact in ERB and put that into the property file (but I don't know if that is even used in the default yaml file). Ideally we would like to have the ec2snitch work, but that snitch then messes with the datacenter name and causes Brisk to halt due to replicas being under the allowed limit. My quesiton is this: is there a custom ec2snitch for Brisk which will fix this or can I fix this some other way (propertyfile snitch if it works and custom facts)? I would like to avoid the propertyfile hack at all costs, but I need to ensure our data is in multiple AZ's.</p> <p>Thanks,<br /> Tom </p>