[SERVER-932] mongos must handle fsync and unlock commands Created: 01/Jan/10  Updated: 12/Jul/16  Resolved: 14/Jul/10

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 1.5.5

Type: Bug Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

it should do something reasonable with them - one option is just return a "not supported" msg and then one must connect directly to the particular mongod server to do these.

it should also be doc'd how these are handled in sharding – keep ticket open until doc'd.



 Comments   
Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: don't allow fsync+lock/unlock through mongos fsync by itselfis ok SERVER-932
http://github.com/mongodb/mongo/commit/08b84d822c7abb27bf20ee5b22580d446d44b5fa

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