[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 |