According to this post[1], one's supposed to start C* with -Dcassandra.renew_counter_id=true as one of the steps of restoring a counter column family. I have two questions related to this:
a) how does that setting affect C* in a non-restoring start? b) if it's < bad > (for some value of that), should I stop C*+remove the setting+start C* after the value has been repaired? c) bonus question: wouldn't it be nice to change the init.d script to be able to add this kind of one-time settings? -- [1] http://www.datastax.com/dev/blog/whats-new-in-cassandra-0-8-part-2-counters -- Marcos Dione SysAdmin Astek Sud-Est pour FT/TGPF/OPF/PORTAIL/DOP/HEBEX @ Marco Polo 04 97 12 62 45 - mdione....@orange.com _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you.