[SERVER-2705] Shell setSlaveOk() returns unhelpful response Created: 08/Mar/11 Updated: 12/Jul/16 Resolved: 07/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.0 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Kyle Banker | Assignee: | Antoine Girbal |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Here's what happens when you call setSlaveOk() from the shell > db.getMongo().setSlaveOk() The response is very confusing, since there's no indication that slave ok has been set to true. |
| Comments |
| Comment by Antoine Girbal [ 07/Oct/11 ] |
|
This was due to SECONDARY> db.test.find() SECONDARY> db.getMongo().setSlaveOk() SECONDARY> db.getMongo().getSlaveOk() |