[SERVER-34922] mongofiles sharded cluster write concern test regression in MongoDB 3.7 Created: 09/May/18 Updated: 06/Dec/22 Resolved: 23/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.6, 4.1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 14.04 |
||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Sprint: | Sharding 2018-07-16 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Recent tools Evergreen tests have started showing a failure in the mongofiles_write_concern_mongos.js test when run against a 3.7 nightly. Nothing relating to mongofiles changed in the tools during the time the failures started and the tests pass when run against MongoDB 3.6.
The test case has 2 nodes of a 3-node shard down, but mongofiles is run with w:1,wtimeout:10000. In the failing case, mongofiles hangs waiting for a database response. Eventually, after several hours, the process is terminated. Note: The mongofiles log output is deceptive, it claims the file is added, but the hang occurs during a deferred close() call when mgo is trying to flush all data to the database and ensure indexes exist. |
| Comments |
| Comment by Kaloian Manassiev [ 23/Jul/18 ] | |||||||
|
Thanks for the analysis blake.oler. I am going to close this ticket as duplicate of | |||||||
| Comment by Blake Oler [ 23/Jul/18 ] | |||||||
|
Two things here:
| |||||||
| Comment by Louis Williams [ 04/Jun/18 ] | |||||||
|
The problematic code is checkDbVersion in create_indexes.cpp, introduced in this commit as part of | |||||||
| Comment by Louis Williams [ 04/Jun/18 ] | |||||||
|
Assigning to sharding | |||||||
| Comment by Louis Williams [ 04/Jun/18 ] | |||||||
|
The hang is happening on createIndexes forĀ dbOne.fs.chunks. It looks the primary is waiting while refreshing the database entry in the catalog cache, which ignores the user's writeConcern.
| |||||||
| Comment by David Golden [ 31/May/18 ] | |||||||
|
This is still a problem as of mongodb-linux-x86_64-ubuntu1404-4.1.0-114-ga3fb68c | |||||||
| Comment by David Golden [ 10/May/18 ] | |||||||
|
Might be related to |