[
https://issues.apache.org/jira/browse/HBASE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557460#comment-13557460
]
Gary Helmling commented on HBASE-7623:
--------------------------------------
Can you describe more what types of errors are causing this or the situations
where it happens?
What ultimately happens when an RPC connection is setup? Does that
successfully obtain and use a username? I think it's important to avoid a
situation where the username for HConnectionKey does not match the
authenticated (even with simple auth) username for an RPC connection.
> Username is not available for HConnectionManager to use in HConnectionKey
> -------------------------------------------------------------------------
>
> Key: HBASE-7623
> URL: https://issues.apache.org/jira/browse/HBASE-7623
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Attachments: trunk-7623.patch
>
>
> Sometimes, some non-IOException prevents User.getCurrent() to get a username.
> It makes it impossible to create a HConnection. We should catch all
> exception here:
> {noformat}
> try {
> User currentUser = User.getCurrent();
> if (currentUser != null) {
> username = currentUser.getName();
> }
> } catch (IOException ioe) {
> LOG.warn("Error obtaining current user, skipping username in
> HConnectionKey",
> ioe);
> }
> {noformat}
> Not just IOException, so that client can move forward.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
