[kudu] branch master updated: [doc] add a note about KUDU-3217 into known issues

[al...@apache.org]

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

alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new 5b113b6  [doc] add a note about KUDU-3217 into known issues
5b113b6 is described below

commit 5b113b68645bd221414f9a975271df2fdc762c27
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Fri Dec 18 19:21:15 2020 -0800

    [doc] add a note about KUDU-3217 into known issues
    
    Change-Id: I2a8fe02e337d62539d30ae4f22377e150b344392
    Reviewed-on: http://gerrit.cloudera.org:8080/16889
    Tested-by: Kudu Jenkins
    Reviewed-by: Hao Hao <ha...@cloudera.com>
---
 docs/known_issues.adoc | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index b35cb38..203b195 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -206,3 +206,10 @@ to communicate only the most important known issues.
   link:https://www.apache.org/legal/resolved.html#category-x[Category X]. This
   issue has been addressed in 1.10.1 and 1.11.1 patch releases correspondingly
   (see link:https://issues.apache.org/jira/browse/KUDU-2990[KUDU-2990]).
+
+* Due to a bug in SSSD PAC plugin of version prior to 1.16, a KRPC connection
+  negotiation may stuck and the whole process wouldn't be able to negotiate
+  any new connection for about 5 minutes in a secure Kudu cluster using SSSD.
+  If using SSSD in secure Kudu cluster deployments, make sure SSSD packages are
+  of version 1.16 or newer
+  (see link:https://issues.apache.org/jira/browse/KUDU-3217[KUDU-3217]).