Description
it was like as a long-running tests.
there is a bug that was posted for this cluster for: MB-5806 stats_collector:handle_info:96] Exception in stats collector
there were a lot of steps before , but i think that are not important here.
the latest steps:
rebalance out 10.3.121.116 node ( 5 nodes in cluster) with some docs operation and queries in parallel
[ns_server:info] [2012-07-06 11:10:00] [ns_1@10.3.121.112:<0.7860.51>:ns_replicas_builder:kill_a_bunch_of_tap_names:219] Killed the following tap names on 'ns_1@10.3.121.115': [<<"replication_building_394_'ns_1@10.3.121.113'">>]
[ns_server:debug] [2012-07-06 11:10:00] [ns_1@10.3.121.112:<0.7017.51>:ns_pubsub:do_subscribe_link:132] Parent process exited with reason {exited,
{'EXIT',<0.7371.51>,
{badmatch,[
[user:info] [2012-07-06 11:10:00] [ns_1@10.3.121.112:<0.20217.0>:ns_orchestrator:handle_info:246] Rebalance exited with reason {exited,
{'EXIT',<0.7371.51>,
{badmatch,[{<19424.31984.25>,killed}
]}}}
[error_logger:error] [2012-07-06 11:10:00] [ns_1@10.3.121.112:error_logger:ale_error_logger_handler:log_report:72]
=========================CRASH REPORT=========================
crasher:
initial call: ns_single_vbucket_mover:mover/6
pid: <0.7859.51>
registered_name: []
exception exit: {exited,
{'EXIT',<0.7011.51>,
{exited,
{'EXIT',<0.7371.51>,
{badmatch,[
in function ns_single_vbucket_mover:mover_inner/6
in call from ns_replicas_builder:try_with_maybe_ignorant_after/2
in call from ns_single_vbucket_mover:mover/6
ancestors: [<0.7011.51>,<0.6935.51>]
messages: [{'EXIT',<0.7011.51>,
{exited,
{'EXIT',<0.7371.51>,
{badmatch,[{<19424.31984.25>,killed}
]}}}}]