[SERVER-19719] Failure to rollback noPadding should not cause fatal error Created: 03/Aug/15 Updated: 24/Aug/15 Resolved: 05/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | 3.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cory Mintz | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | mms-s | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Quint Iteration 7 | ||||||||
| Participants: | |||||||||
| Description |
|
MongoDB 3.0 deprecated usePowerOf2Sizes for noPadding. The fix was not updated, causing this fatal error to return when switching to use of the new field. |
| Comments |
| Comment by Githook User [ 06/Aug/15 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by Githook User [ 05/Aug/15 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by Daniel Pasette (Inactive) [ 03/Aug/15 ] |
|
Just saw that this is already fixed in 3.1.7 – this will be a direct 3.0.6 patch. |