[
https://issues.apache.org/jira/browse/HADOOP-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286959#comment-16286959
]
Bharat Viswanadham commented on HADOOP-9747:
--------------------------------------------
[~daryn]
Thanks for comments.
Intentional. If a specific ticket cache is defined, it must be used. It's wrong
set a property for one of the locations to look and then specify default cache
which means it might find a ticket cache somewhere other than specifically
defined. Not to mention a system property has the same thread-safety issues as
the statics I removed.
Got it, if Krb5CCName is set, now using useCCache and using that location,
{code:java}
put(LoginParam.TICKET_CACHE, System.getenv("KRB5CCNAME")); // 1801
if (ticketCache != null) { //1970
options.put("useCcache", prependFileAuthority(ticketCache));
}
{code}
if Krb5CCName is not set or ticketCache is null, then set useDefaultCcache to
true and use it.
{code:java}
final String ticketCache = params.get(LoginParam.TICKET_CACHE); //1952
if (ticketCache != null) {
options.put("useCcache", prependFileAuthority(ticketCache));
} else {
options.put("useDefaultCcache", "true");
}
}
{code}
So, in this way this issue has been addressed in this patch?
> Reduce unnecessary UGI synchronization
> --------------------------------------
>
> Key: HADOOP-9747
> URL: https://issues.apache.org/jira/browse/HADOOP-9747
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0-alpha1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-9747-trunk.01.patch,
> HADOOP-9747.2.branch-2.patch, HADOOP-9747.2.trunk.patch,
> HADOOP-9747.branch-2.patch, HADOOP-9747.trunk.patch
>
>
> Jstacks of heavily loaded NNs show up to dozens of threads blocking in the
> UGI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
