[SERVER-3923] Compact command on secondary with nonexistent collection leaves secondary in recovery state Created: 22/Sep/11  Updated: 11/Jul/16  Resolved: 22/Sep/11

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: 2.0.0
Fix Version/s: 2.1.0

Type: Bug Priority: Major - P3
Reporter: Kyle Banker Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will stay in recovery mode.


Issue Links:
Depends
is depended on by SERVER-4329 uncaught exception in mapreduce cause... Closed
Duplicate
is duplicated by SERVER-4210 Compact that even failed to start lea... Closed
Operating System: ALL
Participants:

 Description   

Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will move to and remain in a recovery state. You want to node to remain in secondary state, but the only way to fix this is to run compact again on a valid collection.



 Comments   
Comment by auto [ 23/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: add try/catch to sharding commands, too SERVER-3923
Branch: master
https://github.com/mongodb/mongo/commit/6f154bdb998e239362ef455cfd220246cc625967

Comment by auto [ 22/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: fix sharding test SERVER-3923
Branch: master
https://github.com/mongodb/mongo/commit/84816a694455521ecd292a23e4072f11258232a8

Comment by auto [ 22/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: fix tests SERVER-3923
Branch: master
https://github.com/mongodb/mongo/commit/03866e5cb8a60a389c1c68eb38ff65a29390c988

Comment by auto [ 22/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: command to get into/out of maintenance mode SERVER-3923

Not that 3923 could ever happen again, but if it did...
Branch: master
https://github.com/mongodb/mongo/commit/62f34935f79a5e43852b102fc7f40e7604532af6

Comment by auto [ 22/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: try/catch around all command calls SERVER-3923
Branch: master
https://github.com/mongodb/mongo/commit/d869bd9bb787707eefd650c6b59ecfdd2686d9d4

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