Michael Ho has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/12291 )

Change subject: IMPALA-8111: [DOCS] Added KRPC-related known issues
......................................................................


Patch Set 1:

(5 comments)

http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml
File docs/topics/impala_known_issues.xml:

http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml@243
PS1, Line 243: impala-7585
IMPALA ?


http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml@244
PS1, Line 244:       <title>The impala user not added to /etc/passwd when LDAP 
is
             :         enabled</title>
one liner ?


http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml@247
PS1, Line 247:         <p>When using Impala with LDAP enabled, a user may hit 
the
             :           following:</p>
             :         <pre>Not authorized: Client connection negotiation 
failed: client connection to 127.0.0.1:27000: SASL(-1): generic failure: 
All-whitespace username.</pre>
             :         <p>The following sequence can lead to the 
<codeph>impala</codeph> user
             :           not being created in <codeph>/etc/passwd</codeph>.<ul>
             :             <li>Time 1: The <codeph>impala</codeph> user is not 
in LDAP. Impala
             :               was installed, and the user 
<codeph>impala</codeph> is created in
             :                 <codeph>/etc/passwd</codeph>.</li>
             :             <li>Time 2: The <codeph>impala</codeph> user is 
added to LDAP.</li>
             :             <li>Time 3: New machine is added.</li>
My original wording wasn't that clear. I rewrote them as follows. Please edit 
as you see fit:

The following sequence can lead to Impala user not being created in /etc/passwd 
on some machines in the cluster.

Time 1: The user "impala" is not in LDAP. Impala service was installed on 
machine 1 and the user "impala" was created in /etc/passwd

Time 2: The user "impala" is added to LDAP

Time 3: A new machine is added to the cluster. When adding Impala service to 
this new machine, adding the user "impala" will fail as it already exists in 
LDAP.

The consequence is that "impala" doesn't exist in /etc/passwd on the new 
machine, leading to the error seen above.


http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml@266
PS1, Line 266: IMPALLA-7298
typo ?


http://gerrit.cloudera.org:8080/#/c/12291/1/docs/topics/impala_known_issues.xml@292
PS1, Line 292: kudu-2198
KUDU ?



--
To view, visit http://gerrit.cloudera.org:8080/12291
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I806bedcb9d16140413bb6a1f42798be9d1b6371c
Gerrit-Change-Number: 12291
Gerrit-PatchSet: 1
Gerrit-Owner: Alex Rodoni <arod...@cloudera.com>
Gerrit-Reviewer: Michael Ho <k...@cloudera.com>
Gerrit-Comment-Date: Tue, 29 Jan 2019 19:30:34 +0000
Gerrit-HasComments: Yes

Reply via email to