Bizarre Cluster Behavior
I have a three-node cluster which I have been loading data into. Currently I have 19930348 items in the cluster. The cluster was started up this morning with the latest community server (got from Amazon Marketplace).
Presently I'm not using the cluster at all -- all three nodes have been pegged at 100% CPU for over an hour and every attempt to "set" from my php sdk fails with a "Temporary error" (same with attempting to create a new doc through the web admin page). Here's the bizarre part: I can call setMulti from php with no problems ;)
Very new to couchbase so don't have the slightest idea where to start with this one.
Looking at the debug log I see a lot of:
[ns_server:debug,2013-01-08T23:20:08.708,email@example.com:compaction_daemon<0.6762.0>:compaction_daemon:handle_info:309]Finished compaction iteration.
[ns_server:debug,2013-01-08T23:20:08.708,firstname.lastname@example.org:compaction_daemon<0.6762.0>:compaction_daemon:schedule_next_compaction:1200]Finished compaction too soon. Next run will be in 30s
Cpu use is coming mostly from memcached and beam.smp
Any help would be appreciated.