[jira] [Created] (HDFS-17514) RBF: Routers keep using cached stateID even when active NN returns unset header

["Simbarashe Dzinamarira (Jira)" <ji...@apache.org>]

Simbarashe Dzinamarira created HDFS-17514:
---------------------------------------------

             Summary: RBF: Routers keep using cached stateID even when active NN returns unset header
                 Key: HDFS-17514
                 URL: https://issues.apache.org/jira/browse/HDFS-17514
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: rbf
            Reporter: Simbarashe Dzinamarira
            Assignee: Simbarashe Dzinamarira


When a namenode that had "dfs.namenode.state.context.enabled" set to true is restart with the configuration set to false, router will keep using a previously cached state ID.

Without RBF
* client that fetched the old stateID could have stale reads even after msyncing
* new clients will go to activate

With RBF
* client that fetched the old stateID could have stale reads as above.
* New clients will also fetch the stale stateID

We need clients that are created after the restart to not fetch the stale stale ID.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org