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

index warning on hidden secondary after first sync

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
      1. Create a new mongo node
      2. Add it as a hidden secondary to an existing cluster
      3. Let it catch up
      4. Connect to it using a mongo client(I tried this with a 3.03 client and a 3.0.7 client)

      • We created a new mongo node.
      • We added it to an existing replica set as a hidden secondary.
      • It went through startup2 and eventually came up as a hidden secondary.
      • Clients connecting to it would receive the following warning. 
        2015-11-06T17:41:46.790+0000 I STORAGE  [initandlisten] WARNING: the collection 'some_db.fs.chunks' lacks a unique index on _id. This index is needed for replication to function properly
2015-11-06T17:41:46.790+0000 I STORAGE  [initandlisten]          To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes

      Looking at the code, it seemed like it was because the index descriptor object had been called even though its destructor had already run.

      Workaround:

      • We restarted the mongod process on the hidden secondary and now new connections don't have that warning.

            Assignee:
            wan.bachtiar@mongodb.com Wan Bachtiar
            Reporter:
            feanil Feanil Patel
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: