http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster Software, Support, and Training for Apache Cassandra en-US Tue, 21 May 2013 20:31:41 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster#post-623 Tue, 08 Nov 2011 10:45:13 +0000 Anonymous 623@http://www.datastax.com/support-forums/ <p>Your solution works well.</p> <p>I downloaded cassandra from the debian source "deb <a href="http://debian.datastax.com/community" rel="nofollow">http://debian.datastax.com/community</a> stable main", so your source :). So this bug does exist in the 1.0.0 version.</p> <p>I don't update to 1.0.2 yet and can't confirm that the problem is solved in it. </p> http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster#post-615 Mon, 07 Nov 2011 17:21:57 +0000 nickmbailey 615@http://www.datastax.com/support-forums/ <p>Where did you download your version of cassandra from? Those logs indicate that the problem is the bug I described previously, however I was under the impression that bug did not exist in cassandra 1.0.2</p> <p>In any case, changing your rpc_address to be the same as listen_address should solve your problem. Cassandra 1.0.2 should be out soon and also solves this problem without requiring changing the rpc_address. </p> http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster#post-614 Mon, 07 Nov 2011 12:50:35 +0000 Anonymous 614@http://www.datastax.com/support-forums/ <p>I'm on 1.0.0. Here you got the only error in my logs :</p> <p>ERROR: Corrupt endpoint range data for node 0.0.0.0 on keyspace XXX: [TokenRange(end_token='68056473384187692692674921486353642291', start_token='34028236692093846346337460743176821145', endpoints=['0.0.0.0']), TokenRange(end_token='0', start_token='136112946768375385385349842972707284582', endpoints=['0.0.0.0']), TokenRange(end_token='136112946768375385385349842972707284582', start_token='102084710076281539039012382229530463436', endpoints=['0.0.0.0']), TokenRange(end_token='102084710076281539039012382229530463436', start_token='68056473384187692692674921486353642291', endpoints=['0.0.0.0']), TokenRange(end_token='34028236692093846346337460743176821145', start_token='0', endpoints=['0.0.0.0'])]</p> <p>This error is present many times, maybe once per node. </p> http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster#post-612 Sat, 05 Nov 2011 15:45:35 +0000 nickmbailey 612@http://www.datastax.com/support-forums/ <p>Are you on 1.0 or 1.0.1? In 1.0.1 there is a bug in cassandra that prevents OpsCenter from working correctly when rpc_address is 0.0.0.0.</p> <p>If that is the case then changing the rpc address to be the same as listen address should solve the problem. Otherwise it would help if you could post any errors you see in the OpsCenter log (/var/log/opscenter/opscenterd.log) </p> http://www.datastax.com/support-forums/topic/opscenter-doesnt-detect-my-cluster#post-611 Sat, 05 Nov 2011 14:23:04 +0000 Anonymous 611@http://www.datastax.com/support-forums/ <p>Hi,</p> <p>I'm not able to monitor my Cassandra 1.0 cluster with the free version of opscenter 1.3. It seems that OpsCenter can't find any node even if it knows the cluster. it displays:</p> <p>My Cluster (Cassandra )</p> <p>Active nodes<br /> 0 nodes</p> <p>Down nodes<br /> 0 nodes</p> <p>I have got 2 nodes with IPs x and y. I installed OpsCenter on the node x. My cluster is correctly installed :</p> <p>nodetool -h localhost ring -&gt;</p> <p>Address DC Rack Status State Load Owns Token<br /> x datacenter1 rack1 Up Normal 7.87 MB 80.00% 0<br /> y datacenter1 rack1 Up Normal 1.43 MB 20.00% ....</p> <p>I configured this 2 nodes with :</p> <p>x (cassandra.yaml) -&gt;<br /> cluster_name: My Cluster<br /> initial_token: 0<br /> seeds: "x"<br /> listen_address: x<br /> rpc_address: 0.0.0.0</p> <p>y (cassandra.yaml) -&gt;<br /> cluster_name: my cluster<br /> initial_token: 34028236692093846346337460743176821145<br /> seeds: "x"<br /> listen_address: y<br /> rpc_address: 0.0.0.0</p> <p>x (opscenterd.conf) -&gt;<br /> interface = myaddresswhichdoesntmatter.com<br /> seed_hosts: x</p> <p>The rest of the configuration is the default one.</p> <p>There is one more weird thing. When I decommission or removeToken of the y node, Opscenter immediatly displays the node x as being up:</p> <p>Active nodes<br /> 1 nodes</p> <p>Down nodes<br /> 0 nodes</p> <p>Any Ideas? Did I do something wrong?</p> <p>Should you need further informations, please let me know. </p>