Either there is something I have misunderstood about membase or a bug can be provoced out in the open.
I have a website backed by 2 membase nodes. (sep. hardware, windows 2008)
I use membase to store web session data and persistent info on how my analysis databases are up to data.
Membase gives the users a parallel experience (thru my webservices which have no state), and the system have the ability to loadbalance requests between multiple webservers.
I also loadbalance the analysis load on my databases via persistent info in mambase.
So I need membase to be reliably persistent.
I use 1 day as timeout for the keys, and updates this timeout on get operations too. (so I get a running window of timeout)
Since i've noticed the fact that keys suddenly are missing from membase, I have been investigating every aspect of my code related to membase.
I use the enyim v2.12 client. (latest)
In writing momment i have the following item stats, that worry me
Active items Replica Items membase1.prod.local.netminers.dk 339 310 membase2.prod.local.netminers.dk 333 322
So i wonder...
If Server 1 goes down now, would I loose 339-322=17 keys?
Right now I have doubts about if membase can work for me.
When I reset my keys I can see the replica works fine (expected) for a couple of minuttes, then suddenly replicas starts missing.
Enyim client settings.
I use the following client config on all systems using membase:
I have installed the membase servers using the guide provided for cloud install, since I wanted to use the name of the server and not a fixed ip. (for easier maintenance and flexibility)
Mayby I'm using membase wrong, or expect another behaviour than its designed for.
Hope anyone can help me out with some advice.