ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Rudyak <irud...@gmail.com>
Subject Re: Cassandra - Ignite Exception
Date Fri, 12 Aug 2016 21:09:30 GMT
Hi Kamal,

Do you have this problem on Ignite-Cassandra module side or on Cassandra
nodes side? If you have it on Ignite-Cassandra module side that could be
because of this:  https://issues.apache.org/jira/browse/CASSANDRA-8387. It
sometimes happen when you start from clean Cassandra cluster without any
keyspaces/tables to store your Ignite caches.

In this situation Ignite-Cassandra module tries to create new
keyspaces/tables in Cassandra and executes CQL statements like "create
table .... if not exists". According to the Cassandra ticket above, when
statement like "create table" is executed simultaneously from multiple
clients (Ignite nodes in our case) it could cause such an error in the log.

Igor Rudyak

On Fri, Aug 12, 2016 at 12:20 PM, vkulichenko <valentin.kulichenko@gmail.com
> wrote:

> Hi Kamal,
> I would ask on the Cassandra forum about this. Can you do this? The
> exception looks very weird to me, because it complains about the mismatch,
> but the IDs are actually equal:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found b2b47bf0-5f94-11e6-867a-cb7beeeeb92c; expected
> b2b1bcd0-5f94-11e6-867a-cb7beeeeb92c)
> -Val
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Cassandra-Ignite-Exception-tp7013p7024.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message