[SERVER-23580] Remove long-dead writebacklisten command from mongod Created: 06/Apr/16 Updated: 25/Jan/17 Resolved: 08/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
The writebacklisten command hasn't performed any action other than to report an error since 3.0. Any sharded cluster upgraded fully to 3.0 or beyond will never issue the command. It's time to delete some dead code. |
| Comments |
| Comment by Githook User [ 08/Apr/16 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: The command only exists now to provide a useful error message during 2.6->3.0 |