Couchbase kept failed in setting new key
I have a giant dataset in my couchbase,
As I was using some Virtual Machines that didn't met the basic requirement of production, I am trying to add the same number of nodes into the cluster, at the same time, removing the old ones.
However the rebalance seems to be stucked, and now they kept on failing to perform any "SET" operation.
Anything to be done?
Thanks, I just noticed that Couchbase will store the metadata of all keys in the RAM.
So I think Couchbase is not suitable for my case.
I'm trying other alternatives, thanks anyway. And I still think that Couchbase is brilliant!
We do at the moment, but we are actively investigating this.
would you prefer an option to store metadata in memory or not depending on the use case? there certainly are many use cases we see where having the metadata would be useful.
i think that storing metadata is good for entries that are frequently used. However, many cases will have data that are time-related and will be seldom used after some time. These data will be huge and wasting a lot of RAM. I cannot conclude which way is the best.
Btw, the JAVA client seems to have memory leak when the Couchbase server's starting be lack of memory. I dunno why, but the memory leak just disappeared when I stop putting anymore data into Couchbase server.
I'm using couchbase-client-1.1.0.
"Giant" for one, is "Small" for another :)
Can you be more specific? How many nodes, what's your bucket quotas and how many and how big items you have.
Particularly do you run 2.0 or 1.8.1? Do you have views ?
Because rebalance may seem to be stuck but is actually progressing, just slowly.
Feel free to file a bug on http://www.couchbase.com/issues/secure/Dashboard.jspa with details.