replication problems / missing entries after setting them
Hey,
currently i'm experiencing replication problems within my cluster (2 server). most of the time the replica item count of my first node is not equal to the active items of the second node. sometimes the problem occurs in both directions. i can't find the reason for this problem. attached some debug informations (73=node1, 75=node2):
- http://kliemeck.de/couch/73-all.log
- http://kliemeck.de/couch/75-all.log
- http://kliemeck.de/couch/73-config.log
- http://kliemeck.de/couch/75-config.log
- http://kliemeck.de/couch/73-tap.log
- http://kliemeck.de/couch/75-tap.log
my second problem is related to both nodes. i created a recording of the communiation between my client and one node. after setting a key, the key is not available again. i checked the expiration date but it is set to 90 minutes. (created the screenshots via wireshark and couchbase extension http://wiki.wireshark.org/Protocols/couchbase). the problem only occurs on keys like "validity:XXXX" and not on any other keys without colon. but i think its the only case where the key is accessed directly after it has beed added. i checked the document view of my bucket and the key exists. any ideas about that? is there a restriction on the length of the key?
packet overview:
packets for setting the key:
packets for getting the key:
thanks for your help!
Hello,
Can you run the cb_collect_info command on all your nodes of your cluster and share them with us?
This is documented here:
http://www.couchbase.com/wiki/display/couchbase/Working+with+the+Couchba...
regards
any ideas? i created an issue: http://www.couchbase.com/issues/browse/MB-7939