On 7 Jan 2011, at 15:43 , <subversion at amdatu.org> <subversion at amdatu.org> wrote:
> Log: > [AMDATU-243] Several clustering related bugfixes: > - The CassandraDaemon service now waits for 5 seconds immediately after > activating the cassandra daemon. This gives the daemon the time to > synchronize data with other nodes in the cluster. Without this timeout, the > synchronization will happen while Amdatu adds keyspaces and columnfamilies > since the casasndra db is empty upon first startup. This caused many sync > issues, which are vanished after adding this timeout. Simply waiting 5 seconds in my opinion is a quick hack at best, but not a proper solution. Why are things going wrong when keyspaces and columnfamilies are added? In a dynamic environment ultimately this can happen at any point in time, so also when synchronizing data because of changes in the cluster configuration. Are these bugs in Cassandra? If so, have we reported them? Greetings, Marcel
