Details
-
Bug
-
Resolution: Incomplete
-
Critical
-
2.0-developer-preview-3
-
None
-
Security Level: Public
-
None
-
- We only have 1 node (4GB of RAM) and 1 bucket ('default' bucket)
- We run Couchbase 2.0 Dev Preview 3
- The server is homed in a large Amazon EC2 instance (2 virtuals cores)
Description
See full description at
http://www.couchbase.org/forums/thread/node-down-impossible-get-it-back
Summary is that after some time under regular workload, the end user sees a protocol violation via the Ruby Client and sees in the log that it the bucket was shutdown and did not restart.
Attachments
| For Gerrit Dashboard: MB-4600 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 155108,1 | MB-46000: Rename target 'check' to 'couchdb_check' | master | couchdb | Status: ABANDONED | 0 | 0 |