Hi,
we are using couchbase enterprise (3 node cluster mode) edition and our databucket used for session storage growed to 30 GB (which is ridicously high - I would expect not more than 500 MB). This would fit nicely into the “append-only” bug described here: http://www.couchbase.com/communities/q-and-a/persistence-becoming-issue-can-it-be-disabled#comment-390
My question is if this should be fixed in version 2.2 or if it is still an open issue? (I couldn’t confirm the issue with a quicklook into the changelog: http://www.couchbase.com/issues/browse/MB?selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel )
If so is there is some kind of workaround (actually we don’t use auto-compactation - which IMHO would only safe some time I think). Some more information:
- couchbase cluster in couchbase mode
- used by client (php) with memcache protocol
Thanks a lot in advance & best, Georg