[SERVER-26824] Skip FSM workloads which rely on nUpserted or nRemoved when Balancer is enabled Created: 28/Oct/16 Updated: 08/Sep/17 Resolved: 26/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.4.0-rc1 |
| Fix Version/s: | 3.4.9, 3.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | tig-concurrency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | TIG 2017-02-13 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
remove_multiple_documents.js (and possibly other FSM workloads) assume that the count returned to the client is correct. For multi-updates and multi-deletes, this is not the case if there is an active migration affecting the modified documents because those operations aren't versioned. We should investigate which tests in the FSM suites are affected and figure out a strategy to make them robust to background migrations. |
| Comments |
| Comment by Githook User [ 10/Aug/17 ] |
|
Author: {'username': 'hptabster', 'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams'}Message: (cherry picked from commit eab4cda3dc8b677624d0a464d55b76a052daebdd) |
| Comment by Githook User [ 26/Jan/17 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |
| Comment by Jonathan Abrahams [ 25/Jan/17 ] |
|
The nRemoved result during a chunk migration may not be accurate, and we'll skip any workload that depends on that, if the balancer is enabled. |