Details

    • Type: Technical task
    • Status: Closed
    • Priority: Blocker
    • Resolution: Duplicate
    • Affects Version/s: 2.0-beta-2
    • Fix Version/s: 2.0.1
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None
    • Environment:
      build 1940
      ec2 m2.2xlarge, 3->4 nodes, ubuntu 12
      10M x 2KB items + views

      Description

      Later saw "Resetting rebalance status since it's not really running" and "Fail Over Warning: Rebalance recommended, some data does not have the desired number of replicas!"

      I tried to rebalance again and got:

      Rebalance exited with reason {unexpected_exit,
      {'EXIT',<0.29378.114>,
      {{{{badmatch,
      {error,

      {error, <<"Partition 279 not in active nor passive set">>}

      }},
      [

      {capi_set_view_manager,handle_call,3}

      ,

      {gen_server,handle_msg,5}

      ,

      {gen_server,init_it,6}

      ,

      {proc_lib,init_p_do_apply,3}

      ]},
      {gen_server,call,
      ['capi_set_view_manager-default',

      {wait_index_updated,279}

      ,
      infinity]}},
      {gen_server,call,
      [

      {'janitor_agent-default', 'ns_1@ec2-54-242-160-13.compute-1.amazonaws.com'}

      ,
      {if_rebalance,<0.29306.114>,
      {wait_index_updated,279}},
      infinity]}}}}

      Probably duplicate of MB-7115 (update: alk says not likely a dupe of MB-7115 (which is emfile related bug))

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        steve Steve Yen added a comment -

        bug-scrub...

        moved to 2.0.1.

        farshid reports that hitting Rebalance manually again succeeds.

        Show
        steve Steve Yen added a comment - bug-scrub... moved to 2.0.1. farshid reports that hitting Rebalance manually again succeeds.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        I was expecting reproduction of original "Unable to listen.." issue here while gathering atop. But I see no traces of this problem in latest diags

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - I was expecting reproduction of original "Unable to listen.." issue here while gathering atop. But I see no traces of this problem in latest diags
        Hide
        dipti Dipti Borkar added a comment -

        Bug scrub: Need to repro

        Show
        dipti Dipti Borkar added a comment - Bug scrub: Need to repro
        Show
        pavelpaulau Pavel Paulau added a comment - "IP address seems to have changed. Unable to listen on 'ns_1@ec2-54-242-160-13.compute-1.amazonaws.com'." "IP address seems to have changed. Unable to listen on 'ns_1@ec2-54-242-160-13.compute-1.amazonaws.com'. (repeated 1 times)" Diags: https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-50-17-133-35.compute-1.amazonaws.com-11232012-144-diag.zip https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-184-73-53-179.compute-1.amazonaws.com-11232012-146-diag.zip https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-54-242-160-13.compute-1.amazonaws.com-11232012-148-diag.zip https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-174-129-74-54.compute-1.amazonaws.com-11232012-149-diag.zip atops: https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-174-129-74-54.compute-1.amazonaws.com.atop https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-184-73-53-179.compute-1.amazonaws.com.atop https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-50-17-133-35.compute-1.amazonaws.com.atop https://s3.amazonaws.com/bugdb/jira/MB-7120/928cc9a4/ec2-54-242-160-13.compute-1.amazonaws.com.atop
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -
        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - MB-7182

          People

          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            Reporter:
            pavelpaulau Pavel Paulau
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes