[DOCS-1713] Docs should explicitly state that slavedelay is not supported in a sharded environment Created: 16/Jul/13 Updated: 17/Jul/13 Resolved: 16/Jul/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chad Tindel | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 31 weeks, 1 day ago |
| Description |
|
http://docs.mongodb.org/manual/tutorial/configure-a-delayed-replica-set-member/ Neither of these documents address the fact that delayed slaves are not supported in a sharded environment. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 16/Jul/13 ] |
|
After a discussion with scotthernandez, I've confirmed that slavedelay is supported on sharded clusters, though because the secondaries don't keep track of balancing, slavedelay might not have the desired effect. |