[SERVER-12] clonecollection.js sometimes fails to clone index as expected Created: 13/Apr/09  Updated: 12/Jul/16  Resolved: 19/May/09

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

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Occasionally the clonecollection.js test detects that an index from the source collection was not cloned to the target collection. Example failure log:

(mongo init):691 [1] != [0] are not equal : expected index missing
throw "[" + a + "] != [" + b + "] are not equal : " + msg;



 Comments   
Comment by Aaron Staple [ 19/May/09 ]

The problem was that sometimes the shell was delayed in adding the index to the source until after the clone was done at the target. The debug check I added earlier eliminated this race condition.

Comment by Aaron Staple [ 05/May/09 ]

I added some more debug info.

Comment by Aaron Staple [ 04/May/09 ]

again:
<http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/186/steps/test_3/logs/stdio>

Comment by Aaron Staple [ 15/Apr/09 ]

Happened again:

<http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/76/steps/test_3/logs/stdio>

Generated at Thu Feb 08 02:52:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.