http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster Software, Support, and Training for Apache Cassandra en-US Sun, 19 May 2013 10:17:13 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-288 Thu, 07 Jul 2011 21:04:49 +0000 joaquin 288@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>This issue may also be related: <a href="https://issues.apache.org/jira/browse/CASSANDRA-2818" rel="nofollow">https://issues.apache.org/jira/browse/CASSANDRA-2818</a>.</p> <p>Since we recently upgraded the versioning architecture we haven't gotten all the kinks out of a hybrid cluster yet. If you could hold off until 0.8.2 releases and Brisk beta3, that would be great.</p> <p>In the meantime however, you can definitely rsync the data to a new cluster and run testing on that cluster if you wish. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-287 Thu, 07 Jul 2011 20:50:32 +0000 agriffith 287@http://www.datastax.com/support-forums/ <p>I have tried shutting down the nodes and bringing them back up. We have a test environment where we started from scratch and still got the error. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-285 Thu, 07 Jul 2011 20:27:51 +0000 joaquin 285@http://www.datastax.com/support-forums/ <p>This looks like it may be this:</p> <p><a href="https://issues.apache.org/jira/browse/CASSANDRA-2860" rel="nofollow">https://issues.apache.org/jira/browse/CASSANDRA-2860</a>.</p> <p>If possible could you perform a full cluster restart? If not, a rolling restart may fix the issue.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-284 Thu, 07 Jul 2011 20:09:50 +0000 agriffith 284@http://www.datastax.com/support-forums/ <p>Here is problem:</p> <p>We have existing cassandra system running now 0.8.1. This is a production system and is not going to change to a beta unknown cassandra version.</p> <p>We want to run hive/pig analytics against data so Brisk is the choice for that. We can't get brisk and existing cluster to work properly.</p> <p>Are there other options for our situation besides running a mixed-workload cluster?</p> <p>Can we create new brisk cluster and replicate data from existing vanilla cluster?</p> <p>Thanks for any help. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-283 Thu, 07 Jul 2011 17:45:44 +0000 joaquin 283@http://www.datastax.com/support-forums/ <p>If you could try running them all with Brisk Beta2 that would be ideal. Cassandra is never supposed to be run in a mixed version state for longer than it takes to do a rolling upgrade. </p> <p>With 0.8.1 and 0.8.0+ running in the same cluster, you wouldn't get a non-working cluster altogether, but one that may develop problems over time. Since we have not fully tested this Cassandra and Brisk hybrid cluster, if you could move them all to be Brisk Beta2 nodes, that would be best. In future releases we hope to include stable Cassandra versions to allow for this type of hybrid clusters. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-282 Thu, 07 Jul 2011 16:38:10 +0000 agriffith 282@http://www.datastax.com/support-forums/ <p>It seems that if that was the case they would all be incompatible. Right now half of them work and half don't. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-281 Thu, 07 Jul 2011 15:55:51 +0000 nickmbailey 281@http://www.datastax.com/support-forums/ <p>I'm not sure that brisk beta2 is compatible with 0.8.1. The version of cassandra in brisk is pre-0.8.1. Any reason you aren't using brisk on all the nodes and just turning off hadoop on some of them? </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-280 Thu, 07 Jul 2011 15:29:53 +0000 agriffith 280@http://www.datastax.com/support-forums/ <p>Brisk beta 2 for the brisk nodes. the cassandra nodes were 0.8.0 and 0.7.6 at one point but everything was removed and all data wiped, then a clean install of 0.8.1 was put on. </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-275 Thu, 07 Jul 2011 00:58:40 +0000 joaquin 275@http://www.datastax.com/support-forums/ <p>What version of Brisk are you running?</p> <p>It seems as though there may be a version mismatch. Is Brisk Beta2 on the Brisk nodes?</p> <p>Have the nodes previously been on any other version than 0.8.1 and Brisk Beta2?</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-274 Thu, 07 Jul 2011 00:58:38 +0000 joaquin 274@http://www.datastax.com/support-forums/ <p>What version of Brisk are you running?</p> <p>It seems as though there may be a version mismatch. Is Brisk Beta2 on the Brisk nodes?</p> <p>Have the nodes previously been on any other version than 0.8.1 and Brisk Beta2?</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/schemas-not-in-agreement-brisk-mixed-workload-cluster#post-273 Thu, 07 Jul 2011 00:18:45 +0000 agriffith 273@http://www.datastax.com/support-forums/ <p>I am getting strange behavior when starting up a mixed workload cluster.</p> <p>6 nodes running vanilla apache cassandra v 0.8.1<br /> 3 nodes running brisk cassandra with hadoop trackers turned on.</p> <p>3 of the vanilla cassandra nodes are in the seed list, 1 of the brisk nodes is in the seed list.</p> <p>The cassandra.yaml config file has been updated to use the brisksimplesnitch on all nodes.</p> <p>Starting all 6 vanilla cassandra nodes appears to work correctly. However, when the first brisk node is brought online, strange things start to happen.</p> <p>nodetool ring shows all nodes in the cluster running.<br /> - if you log into the brisk node with the cassandra-cli 3 of the vanilla cassandra nodes are unreachable.<br /> - if you log into a reachable cassandra node with the cassandra-cli all 7 nodes show up (6 vanilla and 1 brisk)<br /> - if you log into an unreachable cassandra node with the cassandra-cli the brisk node is unreachable</p> <p>2 of the unreachable vanilla cassandra nodes are seeds, and 1 is a non seed.</p> <p>There is an info message in the cassandra log on these nodes:<br /> INFO [Thread-18] 2011-07-06 22:37:56,958 IncomingTcpConnection.java (line 110) Received connection from newer protocol version. Ignorning message.</p> <p>This is not showing up on the reachable nodes.</p> <p>I have tried bringing up the nodes in different order. When bring up 1 vanilla and 1 brisk I get a different problem. When the brisk node starts it chooses one of the down vanilla cassandra seed nodes as the job tracker. When all vanilla cassandra nodes are up, and the brisk node is started, it chooses the brisk node as the job tracker.</p> <p>Any ideas on what is causing this behavior? </p>