After simulated failure, can't do any operations
Wed, 02/02/2011 - 10:31
I tried simulating a membase server failure by shutting down the windows process and starting it again. My java client connected successfully after the process was back on. However, all my attempts timed out and wasn't able to do any get or put operations despite being connected. So I restarted the entire operating system and tried some get and put operations again while being connected to membase and it just keeps timing out.
The next step was to use a completely different java client (spymemcached) and see if that was the issue. Turns out the client is able to connect but again, times out like the previous scenario. The membase logs inside the web console doesn't have anything alarming.
Any thoughts?
Thanks in advance.
Hmm, that does sound particularly odd. A good test would be to telnet to the particular port and try to run the 'stats' command. If that returns, the problem is likely somewhere in the client. If not, the problem is likely somewhere in the server.
Also, depending on the amount of data, the server needs to take some time to load it all into memory before being able to serve traffic. I "think" an error should be returned rather than timing out, but will have to verify that.
Perry
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Couchbase: http://www.couchbase.com/products-and-services/overview
Call or email "sales -at- couchbase-dot- com" today!