[
https://issues.apache.org/jira/browse/HDFS-17514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846340#comment-17846340
]
ASF GitHub Bot commented on HDFS-17514:
---------------------------------------
simbadzina commented on PR #6804:
URL: https://github.com/apache/hadoop/pull/6804#issuecomment-2110488809
Failing tests in continuous-integration unrelated to my changes
```
Failed junit tests
|
hadoop.hdfs.server.federation.router.security.token.TestSQLDelegationTokenSecretManagerImpl
| hadoop.hdfs.server.federation.store.driver.TestStateStoreMySQL
```
> 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
> Labels: pull-request-available
>
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
