elastic_admin keyspace issues about elassandra HOT 3 CLOSED

Hi
It seems that there is no datacenter defined in your gossip property file sntich (see nullpointerexception in GossipPropertyFileSnitch.getDatacenter() . Could you check your cassandra configuration ?
Thanks',
Vincent.

from elassandra.

Hi,
I am trying to get a single node instance running so I changed the endpoint_snitch to SimpleSnitch. That got rid of the nullpointerexception in GossipPropertyFileSnitch.getDatacenter(). However there is still an error for the elasticadmin keyspace. Here is the log file for the initial startup.

After killing the process and restarting there is not an issue with the keyspace. I double checked that elastic_admin keyspace was created and it was. When I went to try to index something it had a similar error. Here is the log file for the attempt at indexing.

Thanks

from elassandra.

The elastic_admin keyspace store the elasticsearch mapping in a table metadata. This keystore rely on a specific replication strategy, the DatacenterReplicationStrategy, which replicate on all node of the configured datacenter. Even if you succeeded to start, the paxos transaction used to update the elasticsearch mapping failed because DatacenterReplicationStrategy initialization failed with the SimpleSnitch. I have never tested this SimpleSnitch with elassandra, and i can try to fix this in august. Right now, you could use the GossipPropertyFileSnitch even in a single node configuration. Thanks'.

from elassandra.