[
https://issues.apache.org/jira/browse/HDFS-17514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simbarashe Dzinamarira updated HDFS-17514:
------------------------------------------
Description:
When a namenode that had "dfs.namenode.state.context.enabled" set to true is
restarted with the configuration set to false, routers will keep using a
previously cached state ID.
Without RBF
* clients that fetched the old stateID could have stale reads even after
msyncing
* new clients will go to the active.
With RBF
* client that fetched the old stateID could have stale reads like above.
* New clients will also fetch the stale stateID and potentially have stale reads
New clients that are created after the restart should not fetch the stale state
ID.
was:
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.
> 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
> Priority: Minor
>
> When a namenode that had "dfs.namenode.state.context.enabled" set to true is
> restarted with the configuration set to false, routers will keep using a
> previously cached state ID.
> Without RBF
> * clients that fetched the old stateID could have stale reads even after
> msyncing
> * new clients will go to the active.
> With RBF
> * client that fetched the old stateID could have stale reads like above.
> * New clients will also fetch the stale stateID and potentially have stale
> reads
> New clients that are created after the restart should not fetch the stale
> state ID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
