accumulo-notifications mailing list archives

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


Christopher Tubbs commented on ACCUMULO-3890:

bq. IMO, CPs should be treated like a static resource

IMO, it should be up to the CP, not us, to determine that. It'd be nice if there were a CachingCredentialProvider,
or StaticCredentialProvider, or similar to offer users the choice.

(BTW, this is something commons-configuration seems to get a bit right... many Configuration
objects have the ability to reload, based on a reloading strategy, and IIRC, there's a default
reloading strategy for Properties files.)

> 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