[DOCS-3471] ReplicaSet state SHUNNED is displayed as REMOVED and should be mentioned as such Created: 26/May/14 Updated: 02/Sep/14 Resolved: 29/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 24 weeks, 1 day ago | ||||||||
| Description |
|
http://docs.mongodb.org/manual/reference/replica-states/ The replica-set state SHUNNED is not a valid state as per the states that is ever shown in replica-set status or in log file. "REMOVED" is the string representation that is visible to anyone outside code enumeration. To be consistent with what users see in runtime, we should be mentioning REMOVED instead of SHUNNED in our documentation. |
| Comments |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Fix typo. Remove unnecessary detail. |
| Comment by Githook User [ 04/Aug/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Fix typo. Remove unnecessary detail. |
| Comment by Githook User [ 29/Jul/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 29/Jul/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |