Details
-
Bug
-
Resolution: Incomplete
-
Major
-
2.0-beta-2
-
Security Level: Public
-
build 1781
Description
1) 2 nodes Loaded 5 million items
2) Switched to mixmode load with ratio: 60/15/20/5 (get, create, update, delete) at 5kops,sec. Item size 512bytes
3) Rebalance in 2 more nodes.
Rebalance fails reporting first that moxi exited and then later that memcached exited. Logs attached, no cores generated.
Snippets from UI log:
Rebalance exited with reason {unexpected_exit,
{'EXIT',<0.28304.160>,
{{badmatch,[
]},
[
,
{misc,try_with_maybe_ignorant_after,2},
{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}}}
....
Port server memcached on node 'ns_1@10.3.3.62' exited with status 137. Restarting. Messages: Wed Oct 3 13:12:30.676594 PDT 3: TAP (Consumer) eq_tapq:anon_138 - disconnected
Wed Oct 3 13:12:31.038559 PDT 3: Schedule cleanup of "eq_tapq:anon_138"
Wed Oct 3 13:12:32.619131 PDT 3: TAP (Consumer) eq_tapq:anon_139 - disconnected
Wed Oct 3 13:12:33.039373 PDT 3: Schedule cleanup of "eq_tapq:anon_139"
....
Port server moxi on node 'ns_1@10.3.3.62' exited with status 137. Restarting. Messages: 2012-10-03 12:03:55: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (13)
2012-10-03 12:03:55: (cproxy_config.c.326) env: MOXI_SASL_PLAIN_PWD (8)
...