[
http://jira.amdatu.org/jira/browse/AMDATU-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10718#comment-10718
]
Ivo Ladage - van Doorn edited comment on AMDATU-252 at 1/18/11 12:31 PM:
-------------------------------------------------------------------------
Unfortunately, Cassandra does not support
notifications/triggers/listeners/events or whatever to notify a node that
columnfamilies or keyspaces have been created, added or removed by another node
in the cluster.
See also
http://www.apacheserver.net/Client-listener-for-Cassandra-Column-Family-Updates-at1032639.htm
and https://issues.apache.org/jira/browse/CASSANDRA-1872
So we probably have to create our own implementation; separate thread analyzing
available keyspaces and columnfamilies and looking for any changes. Currently
the cassandra daemon supports:
- add keyspace
- drop keyspace
- add CF
- update CF
But we only need to provide a solution that;
- Registers a new CassandraPersistenceManager when a keyspace has been added by
another node in the cluster
- Registers a new ColumnFamilyAvailable when a CF has been added by another
node in the cluster
So that's pretty doable
was (Author: ivol):
Unfortunately, Cassandra does not support
notifications/triggers/listeners/events or whatever to notify a node that
columnfamilies or keyspaces have been created, added or removed by another node
in the cluster.
See also
http://www.apacheserver.net/Client-listener-for-Cassandra-Column-Family-Updates-at1032639.htm
So we probably have to create our own implementation; separate thread analyzing
available keyspaces and columnfamilies and looking for any changes. Currently
the cassandra daemon supports:
- add keyspace
- drop keyspace
- add CF
- update CF
But we only need to provide a solution that;
- Registers a new CassandraPersistenceManager when a keyspace has been added by
another node in the cluster
- Registers a new ColumnFamilyAvailable when a CF has been added by another
node in the cluster
So that's pretty doable
> New Persistence Manager and ColumnFamilyAvailable service not registered from
> keyspaces and CF's created from another node in the cluster
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-252
> URL: http://jira.amdatu.org/jira/browse/AMDATU-252
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Cassandra
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> If we have a cassandra cluster of nodes A and B and a new keyspace or CF is
> added on node A, no persistence manager or ColumnFamilyAvailable service will
> be registered onto node B. This could only be achieved when node B actively
> listens to keyspaces and columnfamilies being created by other nodes in the
> cluster.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
