[jira] [Resolved] (ACCUMULO-3634) AuthenticationTokenSecretManager might delete key while ZooAuthenticationKeyWatcher enumerates existing keys

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved ACCUMULO-3634.
----------------------------------
    Resolution: Fixed

> AuthenticationTokenSecretManager might delete key while ZooAuthenticationKeyWatcher enumerates existing keys
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3634
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3634
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Noticed the following race condition.
> The secret manager (in the master) on startup will enumerate the old keys used for creating delegation tokens and delete the keys that are expired.
> At the same time, the watcher (in each tserver) might see some updates to these keys and update the secret manager. There's a race condition there that the watcher might try to read a key that the secret manager just deleted.
> Need to catch the NoNodeException in the watcher and just accept that it's ok if one of these children are deleted to avoid a scary error in the monitor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)