[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn updated AMDATUCASSANDRA-127:
---------------------------------------------------
Attachment: AMDATUCASSANDRA-127.patch
> Automatic keyspace/CF creation causes schema mismatch in multi-tenant clusters
> ------------------------------------------------------------------------------
>
> Key: AMDATUCASSANDRA-127
> URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-127
> Project: Amdatu Cassandra
> Issue Type: Bug
> Components: Cassandra daemon
> Affects Versions: 0.2.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.1
>
> Attachments: AMDATUCASSANDRA-127.patch
>
>
> I have a 3-node cluster with 5 tenants. When I just boot Amdatu, I get a lot
> of errors concerning schema disagreements, like:
> org.apache.felix.log.LogException:
> org.amdatu.cassandra.application.ThriftException:
> SchemaDisagreementException()
> Context information:
> keyspace = 'Default3'
> columnfamily = 'Gadget'
> at
> org.amdatu.cassandra.application.service.CassandraDaemonServiceImpl.addColumnFamily(CassandraDaemonServiceImpl.java:394)
> and
> InvalidRequestException(why:oAuthServiceConsumer already exists in keyspace
> Default)
> Context information:
> keyspace = 'Default'
> columnfamily = 'oAuthServiceConsumer'
> These pages explain why these errors appear:
> http://wiki.apache.org/cassandra/LiveSchemaUpdates
> http://www.datastax.com/dev/blog/whats-new-cassandra-07-live-schema-updates
> https://issues.apache.org/jira/browse/CASSANDRA-1335
> https://issues.apache.org/jira/browse/CASSANDRA-1391
> The problem is that concurrent schema modification is not supported in
> Cassandra 0.8, which is exactly what happens when booting new nodes in the
> cluster. Schema modifications are handles in background threads and there is
> no way you can obtain a write lock to modify a schema.
> In Cassandra 1.1 concurrent schema modification might be supported (see
> https://issues.apache.org/jira/browse/CASSANDRA-1391). For the time being we
> need an alternative way to resolve this issue.
> NB: this WIKI page describes how to setup a 3-node consistent and redundant
> cluster:
> http://www.amdatu.org/confluence/display/Amdatu/Use+case+4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
