[SERVER-21881] dbhash checking in FSM framework doesn't handle TTL deletes Created: 13/Dec/15 Updated: 21/Nov/16 Resolved: 09/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | 3.2.4, 3.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||
| Sprint: | QuInt E (01/11/16), Query F (02/01/16), Query 10 (02/22/16) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
It's possible for the dbhash checking in the FSM framweork to race with the TTL monitor on a replica set node, which could result in spurious failures. |
| Comments |
| Comment by Githook User [ 20/Feb/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: The fsync+lock operation prevents the TTL monitor from running on the (cherry picked from commit 41f296cdc37f92f8de0ea3d17109693c4f0befb6) |
| Comment by Githook User [ 09/Feb/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: This reverts commit b06952729f5388419f1688e152273b9bb2910739. |
| Comment by Githook User [ 09/Feb/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: The fsync+lock operation prevents the TTL monitor from running on the |
| Comment by Githook User [ 06/Jan/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: |