accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2200) Implement blocking password change
Date Wed, 15 Jan 2014 19:40:35 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872499#comment-13872499
] 

Christopher Tubbs commented on ACCUMULO-2200:
---------------------------------------------

This issue affects more than just password changes. The problem is basically that there's
no good (scalable) way to expire the ZooKeeper cache in one JVM after a change is made in
a different JVM. For the narrow scope of this issue, we could probably have the ZKAuthenticator
expire its cache on failure and retry, before actually returning an authentication failure.
This strategy seems to be used elsewhere (table operations) and works reasonably well.

> Implement blocking password change
> ----------------------------------
>
>                 Key: ACCUMULO-2200
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2200
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Mike Drob
>             Fix For: 1.7.0
>
>
> We should have a blocking password change method that users can use. Our tests would
benefit from this by no longer needing to use blind sleep statements, and users could be assured
that the change has propogated before starting up other clients.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message