[DOCS-7764] Deprecate Master/Slave in sharded environments Created: 27/Apr/16 Updated: 11/Jan/17 Resolved: 28/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Osmar Olivo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 41 weeks, 6 days ago |
| Description |
|
Master/Slave functionality is not compatible with changes being made to the sharding infrastructure going forward. As such, Master/Slave functionality may not be supported in sharded environments in the future. We would like to deprecate this functionality as of right now, so as to give users an opportunity to find alternatives and reach out to us to discuss their use cases such that we can make sure they are fully covered before removing the functionality. |
| Comments |
| Comment by Githook User [ 28/Apr/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 28/Apr/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |