accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry McCay (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3890) Use of CredentialProvider results in a lot of NN ops
Date Mon, 08 Jun 2015 19:36:00 GMT


Larry McCay commented on ACCUMULO-3890:

Hmmm, I thought that the cache was complete removed from CredentialProvider API.
Seems like we are actually encountering some thrashing that would benefit from a cache?

I never thought that caching was as needed for passwords as much as for keys and assumed the
type of scenario that [~billie.rinaldi] describes in the description of this jira.

We can certainly add caching back in for credentials if that makes sense.
I think that Sean's question of what to do when things change makes sense - we shouldn't have
to restart a server to get a new password configuration.

> Use of CredentialProvider results in a lot of NN ops
> ----------------------------------------------------
>                 Key: ACCUMULO-3890
>                 URL:
>             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.6.3, 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

View raw message