[SERVER-22823] authCommands.js failure - shard filtered and unfiltered doc count mismatch after migration Created: 04/Feb/16  Updated: 10/Mar/17  Resolved: 24/Feb/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.0.13, 3.2.13, 3.3.3

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File authCommands.log    
Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Completed:
Backport Requested:
v3.2
Sprint: Sharding 10 (02/19/16), Sharding 11 (03/11/16)
Participants:
Linked BF Score: 0

 Description   

Test failure just due to timing issues, the range deleter was still running but just hadn't quite finished by the time the test errored out.

sharding_WT failed on linux-64-debug

authCommands.js - Logs | History

BF Ticket Generated by renctan

2016-02-04T16:01:33.482+0000 Waiting for migration cleanup to occur...
2016-02-04T16:01:33.633+0000 d20760| 2016-02-04T16:01:33.538+0000 I COMMAND  [conn10] command local.oplog.rs command: getMore { getMore: 17347377553, collection: "oplog.rs", maxTimeMS: 5000, term: 1, lastKnownCommittedOpTime: { ts: Timestamp 1454601692000|4, t: 1 } } cursorid:17347377553 keyUpdates:0 writeConflicts:0 numYields:0 nreturned:1 reslen:493 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, oplog: { acquireCount: { r: 1 } } } protocol:op_command 166ms
2016-02-04T16:01:33.856+0000 assert.soon failed: function (){
2016-02-04T16:01:33.857+0000     print( "Waiting for migration cleanup to occur..." )
2016-02-04T16:01:33.857+0000     return testDB.foo.find().itcount() == testDB.foo.count();
2016-02-04T16:01:33.857+0000 }
2016-02-04T16:01:33.857+0000 doassert@src/mongo/shell/assert.js:15:14
2016-02-04T16:01:33.857+0000 assert.soon@src/mongo/shell/assert.js:176:13
2016-02-04T16:01:33.858+0000 doTest@jstests/sharding/authCommands.js:84:1
2016-02-04T16:01:33.858+0000 @jstests/sharding/authCommands.js:299:1
2016-02-04T16:01:33.858+0000 
2016-02-04T16:01:33.858+0000 2016-02-04T16:01:33.856+0000 E QUERY    [thread1] Error: assert.soon failed: function (){
2016-02-04T16:01:33.859+0000     print( "Waiting for migration cleanup to occur..." )
2016-02-04T16:01:33.859+0000     return testDB.foo.find().itcount() == testDB.foo.count();
2016-02-04T16:01:33.859+0000 } :
2016-02-04T16:01:33.859+0000 doassert@src/mongo/shell/assert.js:15:14
2016-02-04T16:01:33.859+0000 assert.soon@src/mongo/shell/assert.js:176:13
2016-02-04T16:01:33.859+0000 doTest@jstests/sharding/authCommands.js:84:1
2016-02-04T16:01:33.860+0000 @jstests/sharding/authCommands.js:299:1
2016-02-04T16:01:33.860+0000 
2016-02-04T16:01:33.860+0000 failed to load: jstests/sharding/authCommands.js



 Comments   
Comment by Githook User [ 10/Mar/17 ]

Author:

{u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}

Message: SERVER-22823 Increase stability of authCommands.js

(cherry picked from commit fb015882a981d69567946661df87cb7398ae12f1)
Branch: v3.2
https://github.com/mongodb/mongo/commit/ee0ff4acca5ac5704eb2208d3b58839c5ce0eb80

Comment by Githook User [ 26/Oct/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-22823 Increase stability of authCommands.js

(cherry picked from commit fb015882a981d69567946661df87cb7398ae12f1)
Branch: v3.0
https://github.com/mongodb/mongo/commit/44ae815066cdee7127ddeff34d3a04d75378fd61

Comment by Spencer Brody (Inactive) [ 21/Sep/16 ]

This is causing test failures on the 3.0 branch.

Comment by Githook User [ 24/Feb/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-22823 Increase stability of authCommands.js
Branch: master
https://github.com/mongodb/mongo/commit/fb015882a981d69567946661df87cb7398ae12f1

Comment by Randolph Tan [ 04/Feb/16 ]

Looks like documents copied over and cleaned up matches up (not in chronological order since deletion is async, but paired up with migration):

d20760| 2016-02-04T16:00:09.822+0000 I SHARDING [conn18] moveChunk number of documents: 1
d20760| 2016-02-04T16:00:11.987+0000 I SHARDING [RangeDeleter] rangeDeleter deleted 1 documents for test.foo from { i: MinKey, j: MinKey } -> { i: 0.0, j: 1.0 }
...
d20760| 2016-02-04T16:00:14.655+0000 I SHARDING [conn18] moveChunk number of documents: 254
d20760| 2016-02-04T16:01:06.291+0000 I SHARDING [RangeDeleter] rangeDeleter deleted 254 documents for test.foo from { i: 0.0, j: 1.0 } -> { i: 25.0, j: 5.0 }
...
d20760| 2016-02-04T16:00:37.124+0000 I SHARDING [conn18] moveChunk number of documents: 128
d20760| 2016-02-04T16:01:23.247+0000 I SHARDING [RangeDeleter] rangeDeleter deleted 128 documents for test.foo from { i: 25.0, j: 5.0 } -> { i: 38.0, j: 3.0 }
...
d20760| 2016-02-04T16:00:49.731+0000 I SHARDING [conn18] moveChunk number of documents: 128
d20760| 2016-02-04T16:01:38.570+0000 I SHARDING [RangeDeleter] rangeDeleter deleted 128 documents for test.foo from { i: 38.0, j: 3.0 } -> { i: 51.0, j: 1.0 }

Generated at Thu Feb 08 04:01:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.