Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0-beta
-
Fix Version/s: 2.0-beta
-
Component/s: couchbase-bucket
-
Security Level: Public
-
Labels:None
Description
Here's what I'm seeing in logs:
[ns_server:info] [2012-06-07 9:46:58] [n_3@10.17.2.163:ns_port_memcached:ns_port_server:log:166] memcached<0.815.0>: Failed to save docs to database, error = error reading file
memcached<0.815.0>: Warning: commit failed, cannot save CouchDB docs for vbucket = 199 rev = 3 error = -4
memcached<0.815.0>: Fatal error in persisting SET ``00967969'' on vb 199!!! Requeue it...
And then memcached continues complaining. Apparently forever. This means we're totally screwed at this point.
Attaching diag from bad node.
[ns_server:info] [2012-06-07 9:46:58] [n_3@10.17.2.163:ns_port_memcached:ns_port_server:log:166] memcached<0.815.0>: Failed to save docs to database, error = error reading file
memcached<0.815.0>: Warning: commit failed, cannot save CouchDB docs for vbucket = 199 rev = 3 error = -4
memcached<0.815.0>: Fatal error in persisting SET ``00967969'' on vb 199!!! Requeue it...
And then memcached continues complaining. Apparently forever. This means we're totally screwed at this point.
Attaching diag from bad node.