[
https://issues.apache.org/jira/browse/HADOOP-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764973#comment-16764973
]
Ayush Saxena commented on HADOOP-16059:
---------------------------------------
Thanx [~jojochuang] for the review!!!
Regarding the performance.
Actually at the datanode side. (SASLParticipant) neither server nor client
cache is there. So whenever a client connects to a datanode the SASLClient
shall be created for any operation say read, write whatever the operation that
a client needs and SASLServer at the dn side. The number of dn's usually tends
to be huge. This is where this cache seems to be useful.
> Use SASL Factories Cache to Improve Performance
> -----------------------------------------------
>
> Key: HADOOP-16059
> URL: https://issues.apache.org/jira/browse/HADOOP-16059
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Critical
> Attachments: HADOOP-16059-01.patch, HADOOP-16059-02.patch,
> HADOOP-16059-02.patch, HADOOP-16059-03.patch, HADOOP-16059-04.patch
>
>
> SASL Client factories can be cached and SASL Server Factories and SASL Client
> Factories can be together extended at SaslParticipant to improve performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
