mirror of https://github.com/apache/lucene.git
SOLR-11658: ZK mentions: 3.4.10->3.4.11. Also fixed CHANGES.txt attribution.
This commit is contained in:
Steve Rowe
parent
c73bc6b145
commit
e6928d857a
|
|
@ -26,7 +26,7 @@ Apache Tika 1.16
|
|||
Carrot2 3.15.0
|
||||
Velocity 1.7 and Velocity Tools 2.0
|
||||
Apache UIMA 2.3.1
|
||||
Apache ZooKeeper 3.4.10
|
||||
Apache ZooKeeper 3.4.11
|
||||
Jetty 9.3.20.v20170531
|
||||
|
||||
Upgrade Notes
|
||||
|
|
@ -235,7 +235,7 @@ Other Changes
|
|||
|
||||
* SOLR-11051: Use disk free metric in default cluster preferences (noble)
|
||||
|
||||
* SOLR-11658: Upgrade ZooKeeper dependency to 3.4.11 (Steve Rowe, Erick Erickson)
|
||||
* SOLR-11658: Upgrade ZooKeeper dependency to 3.4.11 (Jason Gerlowski, Steve Rowe, Erick Erickson)
|
||||
|
||||
================== 7.2.1 ==================
|
||||
|
||||
|
|
|
|||
|
|
@ -146,7 +146,7 @@ The `.der` files that are output from Step 2 should then be loaded to ZooKeeper
|
|||
|
||||
At the current time, you can only use the ZooKeeper `zkCli.sh` (or `zkCli.cmd` on Windows) script to issue these commands (the Solr version has the same name, but is not the same). If you have your own ZooKeeper ensemble running already, you can find the script in `$ZK_INSTALL/bin/zkCli.sh` (or `zkCli.cmd` if you are using Windows).
|
||||
|
||||
NOTE: If you are running the embedded ZooKeeper that is included with Solr, you *do not* have this script already; in order to use it, you will need to download a copy of ZooKeeper v3.4.10 from http://zookeeper.apache.org/. Don't worry about configuring the download, you're just trying to get the command line utility script. When you start the script, you will connect to the embedded ZooKeeper.
|
||||
NOTE: If you are running the embedded ZooKeeper that is included with Solr, you *do not* have this script already; in order to use it, you will need to download a copy of ZooKeeper v3.4.11 from http://zookeeper.apache.org/. Don't worry about configuring the download, you're just trying to get the command line utility script. When you start the script, you will connect to the embedded ZooKeeper.
|
||||
|
||||
To load the keys, you will need to connect to ZooKeeper with `zkCli.sh`, create the directories, and then create the key file, as in the following example.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ Shutting down a redundant Solr instance will also shut down its ZooKeeper server
|
|||
The solution to this problem is to set up an external ZooKeeper ensemble. Fortunately, while this process can seem intimidating due to the number of powerful options, setting up a simple ensemble is actually quite straightforward, as described below.
|
||||
|
||||
.How Many ZooKeepers?
|
||||
[quote,ZooKeeper Administrator's Guide,http://zookeeper.apache.org/doc/r3.4.10/zookeeperAdmin.html]
|
||||
[quote,ZooKeeper Administrator's Guide,http://zookeeper.apache.org/doc/r3.4.11/zookeeperAdmin.html]
|
||||
____
|
||||
"For a ZooKeeper service to be active, there must be a majority of non-failing machines that can communicate with each other. *To create a deployment that can tolerate the failure of F machines, you should count on deploying 2xF+1 machines*. Thus, a deployment that consists of three machines can handle one failure, and a deployment of five machines can handle two failures. Note that a deployment of six machines can only handle two failures since three machines is not a majority.
|
||||
|
||||
|
|
@ -36,7 +36,7 @@ It is generally recommended to have an odd number of ZooKeeper servers in your e
|
|||
|
||||
For example, if you only have two ZooKeeper nodes and one goes down, 50% of available servers is not a majority, so ZooKeeper will no longer serve requests. However, if you have three ZooKeeper nodes and one goes down, you have 66% of available servers available, and ZooKeeper will continue normally while you repair the one down node. If you have 5 nodes, you could continue operating with two down nodes if necessary.
|
||||
|
||||
More information on ZooKeeper clusters is available from the ZooKeeper documentation at http://zookeeper.apache.org/doc/r3.4.10/zookeeperAdmin.html#sc_zkMulitServerSetup.
|
||||
More information on ZooKeeper clusters is available from the ZooKeeper documentation at http://zookeeper.apache.org/doc/r3.4.11/zookeeperAdmin.html#sc_zkMulitServerSetup.
|
||||
|
||||
== Download Apache ZooKeeper
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ The first step in setting up Apache ZooKeeper is, of course, to download the sof
|
|||
====
|
||||
When using stand-alone ZooKeeper, you need to take care to keep your version of ZooKeeper updated with the latest version distributed with Solr. Since you are using it as a stand-alone application, it does not get upgraded when you upgrade Solr.
|
||||
|
||||
Solr currently uses Apache ZooKeeper v3.4.10.
|
||||
Solr currently uses Apache ZooKeeper v3.4.11.
|
||||
====
|
||||
|
||||
== Setting Up a Single ZooKeeper
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@
|
|||
// specific language governing permissions and limitations
|
||||
// under the License.
|
||||
|
||||
This section describes using ZooKeeper access control lists (ACLs) with Solr. For information about ZooKeeper ACLs, see the ZooKeeper documentation at http://zookeeper.apache.org/doc/r3.4.10/zookeeperProgrammers.html#sc_ZooKeeperAccessControl.
|
||||
This section describes using ZooKeeper access control lists (ACLs) with Solr. For information about ZooKeeper ACLs, see the ZooKeeper documentation at http://zookeeper.apache.org/doc/r3.4.11/zookeeperProgrammers.html#sc_ZooKeeperAccessControl.
|
||||
|
||||
== About ZooKeeper ACLs
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue