[SERVER-21357] index warning on hidden secondary after first sync Created: 09/Nov/15  Updated: 09/Dec/15  Resolved: 09/Dec/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Feanil Patel Assignee: Wan Bachtiar
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20796 Warning on replica that collection la... Closed
Operating System: ALL
Steps To Reproduce:
  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)
Participants:

 Description   
  • 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.


 Comments   
Comment by Wan Bachtiar [ 09/Dec/15 ]

Hi Feanil,

We haven’t heard back from you for some time, so I am going to mark this ticket as resolved.
If this is still an issue for you, feel free to re-open the ticket and provide additional information.

Regards,

Wan.

Comment by Wan Bachtiar [ 24/Nov/15 ]

feanil , Can you please send the logs for :

  • The secondary that is missing indexes. From the time it was started until it has become a secondary.
  • The primary. Around the same time as the secondary log file above.

Also, what MongoDB version running on the primary and the secondary ?

Regards,
Wan.

Generated at Thu Feb 08 03:57:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.