Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.5.1
-
None
-
4.5.1-2806
-
Untriaged
-
-
Yes
Description
From MB-19677, Aliaksey observed the following reason for compactor exiting unexpectedly:
it seems that memcached closed the socket on us. It's not something that we expect, so it's correct to let user know about.
This also leads to logs being flooded with messages about compactor exiting unexpectedly.
Compactor for vbucket `default/986` (pid [{type,vbucket},
|
{name,<<"default/986">>},
|
{important,false},
|
{fa,
|
{#Fun<compaction_new_daemon.13.102846360>,
|
[<<"default">>,
|
{986,<<"default/986">>},
|
{config,
|
{30,undefined},
|
{30,undefined},
|
undefined,false,false,
|
{daemon_config,30,131072,
|
20971520}},
|
false,
|
{1471025460,720653,false}]}}])
|
...
|
=========================CRASH REPORT=========================
|
crasher:
|
initial call: compaction_new_daemon:-spawn_vbucket_compactor/5-fun-0-/0
|
pid: <0.17618.339>
|
registered_name: []
|
exception error: no match of right hand side value {error,closed}
|
in function mc_client_binary:cmd_vocal_recv/5 (src/mc_client_binary.erl, line 156)
|
in call from mc_client_binary:compact_vbucket/5 (src/mc_client_binary.erl, line 406)
|
in call from ns_memcached:'-compact_vbucket/3-fun-0-'/5 (src/ns_memcached.erl, line 1514)
|
in call from ns_memcached:'-perform_very_long_call/2-fun-0-'/2 (src/ns_memcached.erl, line 322)
|
in call from misc:'-executing_on_new_process/1-fun-0-'/3 (src/misc.erl, line 1555)
|
ancestors: [<0.15285.339>,<0.15275.339>,<0.14956.339>,<0.14953.339>,
|
<0.14979.339>,compaction_new_daemon,ns_server_sup,
|
ns_server_nodes_sup,<0.12782.335>,ns_server_cluster_sup,
|
<0.89.0>]
|
|
