Re: Error connection to remote JMX agent! on nodetool

2011-03-24 Thread aaron morton
Simple solution is to stop the nodes and delete the contents of the commitlog, data and saved_caches directories. Normally these are in /var/lib/cassandra This will give you a clean starting point. The cli statement is using secondary indexes http://www.datastax.com/dev/blog/whats-new-cassand

Re: Error connection to remote JMX agent! on nodetool

2011-03-24 Thread ko...@vivinavi.com
Hi Aaron Thank you so much for your reply and advice. I did describe cluster. Then I found multiple version as following. [default@unknown] describe cluster; Cluster Information: Snitch: org.apache.cassandra.locator.SimpleSnitch Partitioner: org.apache.cassandra.dht.RandomPartitioner Sc

Re: Error connection to remote JMX agent! on nodetool

2011-03-23 Thread aaron morton
If you are getting the "Cluster schema does not agree" then you have a sick cluster and replication will not be working properly. Open the cassandra-cli client and type "describe cluster;" you should see a single schema version such as... [default@unknown] describe cluster; Cluster Informatio

Re: Error connection to remote JMX agent! on nodetool

2011-03-23 Thread ko...@vivinavi.com
Hi Aaron Thank you so much for your reply and advice. I watched your presentation. it"s helpful for me. Anyway I did as following with 2 node servers.(53;1st node,54;2nd node) I started the following write/read.php program by through Thrift at 53 server. $users->insert($Key, array('Movie'

Re: Error connection to remote JMX agent! on nodetool

2011-03-23 Thread Aaron Morton
What process are you using to confirm the data was replicated to another server ? And what makes you say the data is not replicated ? I think your understanding of the replication may be a little off, you rarely read from one node. Have a look at http://thelastpickle.com/2011/02/07/Introduction

Re: Error connection to remote JMX agent! on nodetool

2011-03-23 Thread ko...@vivinavi.com
Hi maki-san I am so sorry this was my mistake. I expected when I set data at one node, the data should be copied to the other node at the same keyspace and same column family by replication. This replication was working. I just made a mistake to get data by wrong Key.(First character of key wa

Re: Error connection to remote JMX agent! on nodetool

2011-03-22 Thread Maki Watanabe
How do you define your Keyspace? As you may know, in Cassandra, replication (factor) is defined as the attribute of Keyspace. And what do you mean: > However replication never happened. > I can't get data I set at other node. What did you do on cassandra, and what did you get in response? maki

Re: Error connection to remote JMX agent! on nodetool

2011-03-22 Thread ko...@vivinavi.com
Hi Sasha Thank you so much for your advice. I changed JMX_PORT from 10036 to 8080 in cassandra-env.sh. Now nodetool ring is working as following. # nodetool --host **.**.254.54 ring Address Status State LoadOwnsToken

Re: Error connection to remote JMX agent! on nodetool

2011-03-18 Thread Sasha Dolgy
You need to specify the -jmxport with nodetool On Mar 19, 2011 2:48 AM, "ko...@vivinavi.com" wrote: > Hi everyone > > I am still new to Cassandra, Thrift. > But anyway Cassandra 0.7.4, Thrift 0.5.0 are working on java 1.6.0.18 of > Debian 5.0.7.at single node. > Then I had to try and check multi n

Error connection to remote JMX agent! on nodetool

2011-03-18 Thread ko...@vivinavi.com
Hi everyone I am still new to Cassandra, Thrift. But anyway Cassandra 0.7.4, Thrift 0.5.0 are working on java 1.6.0.18 of Debian 5.0.7.at single node. Then I had to try and check multi node on 2 servers. (JVM_PORT=10036 on /etc/cassandra-env.sh) I modified /etc/cassandra/cassandra.yaml as followin