Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31688

W SHARDING [conn161595] can't accept new chunks because there are still 1 deletes from previous migration

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Centos7.2

      in mongo cluster have 8 shard, As the "chunk" distribution is uneven, so i check mongos log or mongod log, found the following messages:

      2017-10-24T14:36:54.135+0800 W SHARDING [conn161595] can't accept new chunks because there are still 1 deletes from previous migration
      2017-10-24T14:36:54.318+0800 I SHARDING [conn161595] Refreshing chunks for collection appdata.App based on version 2133|4||5731b54b1f4029ea4c489504
      2017-10-24T14:36:54.321+0800 I SHARDING [CatalogCacheLoader-16123] Refresh for collection appdata.App took 2 ms and found version 2133|4||5731b54b1f4029ea4c489504
      2017-10-24T14:36:54.321+0800 W SHARDING [conn161595] can't accept new chunks because there are still 1 deletes from previous migration
      2017-10-24T14:36:54.328+0800 I SHARDING [conn161599] Refreshing chunks for collection appdata.AppTrend based on version 3933|22||5731b7bc1f4029ea4c48954e
      2017-10-24T14:36:54.330+0800 I SHARDING [CatalogCacheLoader-16125] Refresh for collection appdata.AppTrend took 2 ms and found version 3933|22||5731b7bc1f4029ea4c48954e
      2017-10-24T14:36:54.332+0800 W SHARDING [conn161599] can't accept new chunks because there are still 1 deletes from previous migration
      2017-10-24T14:36:54.386+0800 I SHARDING [conn161597] Refreshing chunks for collection appdata.SearchWordHistoryUS based on version 1216|256||59360a83e1421c1ec352de6f
      2017-10-24T14:36:54.391+0800 I SHARDING [CatalogCacheLoader-16123] Refresh for collection appdata.SearchWordHistoryUS took 4 ms and found version 1216|256||59360a83e1421c1ec352de6f
      2017-10-24T14:36:54.393+0800 W SHARDING [conn161597] can't accept new chunks because there are still 1 deletes from previous migration
      2017-10-24T14:36:54.530+0800 I SHARDING [conn161598] Refreshing chunks for collection appdata.ASORank based on version 233434|5215||56f8eab11f4029ea4c3d4ccc
      2017-10-24T14:36:54.547+0800 I SHARDING [conn161599] Refreshing chunks for collection appdata.ASORankUS based on version 49871|5445||594901feaa03025ae98e1d0c
      2017-10-24T14:36:54.588+0800 I SHARDING [CatalogCacheLoader-16123] Refresh for collection appdata.ASORankUS took 40 ms and found version 49871|5445||594901feaa03025ae98e1d0c

      so how can i found the previous migration chunk and deletes it with manually, and is there any way to solve this problem without restart a shard?

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            vegaoqiang vegaoqiang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: