This is an automated email from the ASF dual-hosted git repository.

manikumar pushed a commit to branch 2.5
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/2.5 by this push:
     new f008dbf  KAFKA-9575: Mention ZooKeeper 3.5.7 upgrade
f008dbf is described below

commit f008dbf9b7fd408b8987b0dd80d44323cdb6b5dc
Author: Ron Dagostino <rdagost...@confluent.io>
AuthorDate: Fri Feb 21 18:45:14 2020 +0530

    KAFKA-9575: Mention ZooKeeper 3.5.7 upgrade
    
    *More detailed description of your change,
    if necessary. The PR title and PR message become
    the squashed commit message, so use a separate
    comment to ping reviewers.*
    
    *Summary of testing strategy (including rationale)
    for the feature or bug fix. Unit and/or integration
    tests are expected for any behaviour change and
    system tests should be considered for larger changes.*
    
    Author: Ron Dagostino <rdagost...@confluent.io>
    
    Reviewers: Reviewers: Manikumar Reddy <manikumar.re...@gmail.com>
    
    Closes #8139 from rondagostino/KAFKA-9575
    
    (cherry picked from commit d9b8b86bdd0b4fe6965b1f597f9ba7ec33954a50)
    Signed-off-by: Manikumar Reddy <maniku...@confluent.io>
---
 docs/upgrade.html | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/upgrade.html b/docs/upgrade.html
index 55593d6..bb30735 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -42,6 +42,16 @@
         enabled by default. You can continue to use TLSv1 and TLSv1.1 by 
explicitly enabling these in the configuration options
         <code>ssl.protocol</code> and <code>ssl.enabled.protocols</code>.
     </li>
+    <li>ZooKeeper has been upgraded to 3.5.7, and a ZooKeeper upgrade from 
3.4.X to 3.5.7 can fail if there are no snapshot files in the 3.4 data 
directory.
+        This usually happens in test upgrades where ZooKeeper 3.5.7 is trying 
to load an existing 3.4 data dir in which no snapshot file has been created.
+        For more details about the issue please refer to <a 
href="https://issues.apache.org/jira/browse/ZOOKEEPER-3056";>ZOOKEEPER-3056</a>.
+        A fix is given in <a 
href="https://issues.apache.org/jira/browse/ZOOKEEPER-3056";>ZOOKEEPER-3056</a>, 
which is to set <code>snapshot.trust.empty=true</code>
+        config in <code>zookeeper.properties</code> before the upgrade.
+    </li>
+    <li>ZooKeeper version 3.5.7 supports TLS-encrypted connectivity to 
ZooKeeper both with or without client certificates,
+        and additional Kafka configurations are available to take advantage of 
this.
+        See <a 
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-515%3A+Enable+ZK+client+to+use+the+new+TLS+supported+authentication";>KIP-515</a>
 for details.
+    </li>
 </ul>
 
 <h4><a id="upgrade_2_4_0" href="#upgrade_2_4_0">Upgrading from 0.8.x, 0.9.x, 
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x 
or 2.3.x to 2.4.0</a></h4>

Reply via email to