[SERVER-23299] Remove temp flag on all collections if last startup was on 3.2.0-3.2.4 Created: 22/Mar/16  Updated: 31/Mar/17  Resolved: 13/Apr/16

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.2.5, 3.3.5

Type: New Feature Priority: Critical - P2
Reporter: Mathias Stearn Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: code-and-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-23274 Collections created with the $out agg... Closed
is related to SERVER-24024 SERVER-23299 patch does not respect q... Closed
is related to SERVER-23514 Remove code and tests from SERVER-23299 Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Sharding 12 (04/01/16), Sharding 13 (04/22/16)
Participants:
Case:
Linked BF Score: 0

 Description   

This is one way to clean up the damage from SERVER-23274.



 Comments   
Comment by Githook User [ 21/Nov/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-23514 remove code and tests from SERVER-23299
Branch: master
https://github.com/mongodb/mongo/commit/eda82cb72e0271604267a9d80f5468d5b0dbc348

Comment by Githook User [ 13/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 Add an arbiter to server-23299-1.js test, to remove flaky behavior.

The multiversion suite's replica set upgrade logic expects sets to have
at least three nodes. Add an arbiter so this test can use said upgrade logic
reliably.

(cherry picked from commit 985d53ebd792481f2443ad14eefdb0d0fbf28eff)
Branch: v3.2
https://github.com/mongodb/mongo/commit/c3b97911a0490581163975a5af13d6141fc684b9

Comment by Githook User [ 13/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 Add an arbiter to server-23299-1.js test, to remove flaky behavior.

The multiversion suite's replica set upgrade logic expects sets to have
at least three nodes. Add an arbiter so this test can use said upgrade logic
reliably.
Branch: master
https://github.com/mongodb/mongo/commit/56a903eb64f5b9865f1b54b90334f02cb5adf6dd

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 Fix lint error in js test.
Branch: v3.2
https://github.com/mongodb/mongo/commit/73d620c9d35ab5d44d35f2602dd48203647b428d

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 When starting mongod, clear temp flags from collections if appropriate.

See the description in SERVER-23299 for the definition of appropriate.

(cherry picked from commit 5e11e4484b84c8f913a4b14b24fbb7c9c46ee40f)
Branch: v3.2
https://github.com/mongodb/mongo/commit/5f23fb00bf69a19b67c385e7e953137c70eaa3e0

Comment by Githook User [ 04/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 When starting mongod, clear temp flags from collections if appropriate.

See the description in SERVER-23299 for the definition of appropriate.
Branch: master
https://github.com/mongodb/mongo/commit/5e11e4484b84c8f913a4b14b24fbb7c9c46ee40f

Comment by Githook User [ 04/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23299 When starting mongod, clear temp flags from collections if appropriate.

See the description in SERVER-23299 for the definition of appropriate.
Branch: master
https://github.com/mongodb/mongo/commit/5e11e4484b84c8f913a4b14b24fbb7c9c46ee40f

Comment by Daniel Pasette (Inactive) [ 28/Mar/16 ]

We already touch every collection and index at startup, so this check shouldn't make an appreciable difference.

Comment by Andy Schwerin [ 28/Mar/16 ]

For systems with very large numbers of collections, none of which need the temp flag cleared, do you think this approach will have an appreciable impact on startup time, redbeard0531? It's only going to happen when transition ing from 3.2.x for x < 5 to a newer release, but if it's going to take a long time, I can make sure to add some affirmative logging.

Generated at Thu Feb 08 04:02:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.