[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:
Related
is related to SERVER-11908 Failure to rollback usePowerOf2Sizes ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Quint Iteration 7
Participants:

 Description   

SERVER-11908 fixed an issue where trying to rollback a collmod usePowerOf2Sizes leaves the server in a fatal state. The issue was fixed by carving out this specific collmod as a logged warning.

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: SERVER-19719 fix rollback_collMod_fatal.js which expected a different log message
Branch: v3.0
https://github.com/mongodb/mongo/commit/da5744a4dba5bdba10e5e5fb63eb27fbf769de0d

Comment by Githook User [ 05/Aug/15 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}

Message: SERVER-19719 Failure to rollback noPadding should not cause fatal error
Branch: v3.0
https://github.com/mongodb/mongo/commit/e1547eaa68014371d1c70e32cc73e3b5ec23e480

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.

Generated at Thu Feb 08 03:51:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.