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

change shard collection's 'expireAfterSeconds' cause moveChunk fail

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.6.5
    • Component/s: Index Maintenance, Sharding
    • None
    • ALL
    • Hide

      In shard cluster
      first, rebuild index with new expire seconds;(I use pymongo driver)
      second, start auto balancer;

      Show
      In shard cluster first, rebuild index with new expire seconds;(I use pymongo driver) second, start auto balancer;
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      mongod version: 2.6.5
      moveChunk from shard0001 to shard0010 fail, warning log at shard0010:
      ----------------------------
      2015-06-05T10:02:27.999+0800 [migrateThread] warning: failed to create index before migrating data. idx: { v: 1, key:

      { _: -1 }

      , name: "__-1", ns: "xx.xx", expireAfterSeconds: 5227200 } error: IndexOptionsConflict Index with name: __-1 already exists with different options
      ----------------------------
      But I check these two shards's _ index they both have same “expireAfterSeconds”.

      After I restart all shards the moveChunk works fine, Is it a 'cached' bug?

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            cswuyg cswuyg
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: