Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
2.0.1
-
None
-
Security Level: Public
-
None
-
Ubuntu 11.10
Description
I have a single node Couchbase 2.0 server, 16gb of RAM allocated to the cluster, with a bucket that expects ~650,000 new key/values a day. Each key/value around 100-200KB.
It seems though that after around 16GB of new writes, the server stops ejecting keys. The "memory used" goes beyond the low watermark (12.8GB) and beyond the high watermark as well (14.5GB) and never backs down.
A disk write issue seems likely, but the disk write queue is empty when the Temp OOM errors start showing up.
I've tried tweaking the low and high water mark values. I've also set the min_data_age to 0.
Still with all this, it after about 16GB of new writes, restarting the server is the only thing that will make it work again.
Here is a screen-cap of the Bucket Analytics where the problem is visible.
https://dl.dropbox.com/u/171745/Couchbase-Console-%282.0.1%29.jpg
I'm attached the cbcollect_info for the server.
Issue created because of the following request:
http://www.couchbase.com/forums/thread/couchbase-stops-ejecting-keys-returns-nothing-temp-oom-errors-until-restarted#comment-1009432