[
https://issues.apache.org/jira/browse/HADOOP-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760774#comment-16760774
]
Ayush Saxena commented on HADOOP-16059:
---------------------------------------
Thanx [~jojochuang] for coming up and giving it a look. :)
This is strictly a performance improvement only. Doesn't fixes a broken stuff ,
neither does it intends to fix something broken. You can check HADOOP-10172 it
finds some relation with the present change.
Regarding the scenario here , would give a brief regarding the scenario , for a
call always the SASLClient is created which goes and fetches up info and
perform several actions which are time consuming . The idea here is to cache
the results and save efforts for the subsequent processing and calls. The
HADOOP-10172 already had it done at the server layer , here I have extended the
scenario at the client layer And even extended the already available server
cache and the newly formed client cache at SASLParticipant level to save the
efforts up there too.
Let me know , if something isn't clear . I shall try my best to clarify.
Pls Review!!!
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
