[SERVER-20580] Failure in csrs_upgrade_during_migrate.js Created: 17/Sep/15 Updated: 25/Jan/17 Resolved: 07/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | csrsupgrade, test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Sharding F (01/29/16) |
| Participants: |
| Description |
|
Failed on a patch build: https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_sharding_WT_e61e8a9cbd3c5c1e5a46fc74f4b5ab5ce879c115_15_09_17_00_00_24 spencer said it was due to a race condition in the test. Logs are attached |
| Comments |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit 43209263a40af233dd1fae25aa719c7b2b304480) |
| Comment by Igor Canadi [ 12/Jan/16 ] |
|
Thanks Spencer! |
| Comment by Spencer Brody (Inactive) [ 12/Jan/16 ] |
|
Sorry about that igor, when I fixed the csrs_upgrade.js test to work with any storage engine supporting committed reads, I forgot to update csrs_upgrade_during_migrate.js as the test was disabled at the time. I just pushed https://github.com/mongodb/mongo/commit/f2d33bbcde359f5caf2e4e66559dcc46b164cd2b which should fix the test to work on the RocksDB variant. |
| Comment by Igor Canadi [ 11/Jan/16 ] |
|
Hey Spencer, csrs_upgrade_during_migrate.js is failing on RocksDB with "No primary or non-WT engine not removed in..." error. The error is thrown here: https://github.com/mongodb/mongo/blob/master/jstests/sharding/csrs_upgrade_during_migrate.js#L189 Is the test designed to only run only on WiredTiger? Or is this a legitimate bug in RocksDB storage engine? |
| Comment by Githook User [ 07/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 23/Sep/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |