[
https://issues.apache.org/jira/browse/ACCUMULO-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575170#comment-14575170
]
Josh Elser commented on ACCUMULO-3890:
--------------------------------------
bq. But there's nothing in the CredentialProvider API that says it needs to be
stored like a file, it could just as easily be a facade in front of an RPC
mechanism.
True, but I would say the API itself lends towards being file-based (but that's
just my opinion). Either way, we can't future proof against any/every
implementation that comes about. We make some reasonable assumptions,
implementation them in a way that works against what exists now, and can
revisit if it is inefficient/insufficient in the future :shrug:. Even an RPC
mechanism, we probably wouldn't want to re-poll it as often as we do now (which
is part of a larger problem in us repeatedly parsing configurations, but that's
another issue).
> Use of CredentialProvider results in a lot of NN ops
> ----------------------------------------------------
>
> Key: ACCUMULO-3890
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3890
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.1, 1.6.2, 1.7.0
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: 1.7.1, 1.8.0
>
>
> Every time we access a sensitive property or iterate over a configuration
> when there is a CredentialProvider configured, it results in NN operations
> (as evidenced by FSNamesystem.audit logs). I think that we could assume the
> CredentialProvider is static, read its properties once and cache them in
> memory to avoid these unnecessary reads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
