[
https://issues.apache.org/jira/browse/ZOOKEEPER-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995892#comment-14995892
]
Hudson commented on ZOOKEEPER-2240:
-----------------------------------
SUCCESS: Integrated in ZooKeeper-trunk #2813 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2813/])
ZOOKEEPER-2240: Make the three-node minimum more explicit in documentation
and on website (Shawn Heisey via rgs) (rgs:
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1713320])
* trunk/CHANGES.txt
* trunk/docs/zookeeperAdmin.html
* trunk/docs/zookeeperStarted.html
> Make the three-node minimum more explicit in documentation and on website
> -------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2240
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2240
> Project: ZooKeeper
> Issue Type: Improvement
> Components: documentation
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Trivial
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2240.patch, ZOOKEEPER-2240.patch
>
>
> One of the most important parts of a production zookeeper deployment is the
> three-node minimum requirement for fault tolerance ... but when I glance at
> the website and the documentation, this requirement is difficult to actually
> find.
> It is buried deep in the admin documentation, in a sentence that says "Thus,
> a deployment that consists of three machines can handle one failure, and a
> deployment of five machines can handle two failures." Other parts of the
> documentation hint at it, but nothing that I've seen comes out and explicitly
> says it.
> Ideally, documentation about this requirement would be in a location where it
> can be easily pinpointed with a targeted URL, so I can point to ZK
> documentation with a link and clearly tell SolrCloud users that this is a
> real requirement.
> If someone can point me to version control locations where I can check out or
> clone the docs and the website, I'm happy to attempt a patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
