Task took too long to execute and other events in log
First of all congratulations on what is a very promising product!
I've been running the various beta versions of Membase on a two node cluster and just upgraded to the latest Membase GE Windows release and Enyim client library yesterday. Since upgrading I've started to notice a number of messages in the logs that seem to suggest there are some issues with the cluster - e.g
#Request with path /diag took too long to execute: 43173 ms
- #Server error during processing: ["web request failed",{path,
-
"/pools/default/buckets/GameScores/stats"},{type,error},{what,badarith},...
-
-
#Port server vbucketmigrator on node 'ns_1@192.168.100.113' exited with status 3 ... Failed to read from stream: Unknown error (repeated 2 times)
-
-
#Control connection to memcached on 'ns_1@192.168.100.113' disconnected: {{badmatch,{error,closed}}
-
-
At a high level do these messages indicate a problem with the cluster / cluster communication or are they just verbose output?
-
-
Many thanks
I seem to be having the same issue. Then the servers get into this state where I can seem to do anything. They will not restart properly and come back up. I can't bring them back online and rebalance. Any idea on what this is and anyfixes immenent?
Some of the messages I am seeing:
Control connection to memcached on 'ns_1@10.168.8.27' disconnected: {{badmatch,
{error,timeout}},[{mc_client_binary,cmd_binary_vocal_recv,5},
{mc_client_binary,select_bucket,2},
{ns_memcached,ensure_bucket,2},
{ns_memcached,handle_info,2},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,
3}]}
Port server memcached on node 'ns_1@10.168.8.67' exited with status 1. Restarting. Messages: Tap client connect closed (69224). Putting it (0A054F20) in pending close
Tap client connect closed (81656). Putting it (0CDA3040) in pending close
Tap client connect closed (86588). Putting it (0B059100) in pending close
Request with path /pools/default/bucketsStreaming/Products took too long to execute: 1362289 ms.
mshapiro,
Can you please also send the output of the following request:
http://<host>:8091/diag where <host> is the IP address or hostname of one of the servers displaying that message.
The output will likely be rather large so you'll want to zip it up before sending/attaching it.
Thanks
Bhawana
Those errors do look like something that needs to be addressed. Can you send over the output of http://<host>:8091/diag where <host> is the IP address or hostname of one of the servers displaying that message?
The output will likely be rather large so you'll want to zip it up before sending/attaching it.
Thanks.
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!