simbadzina opened a new pull request, #6804:
URL: https://github.com/apache/hadoop/pull/6804
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
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.
### How was this patch tested?
New unit test
Unit test fails with the patch is PoolAlignmentContext in the second commit.
Unit test pass with the patch.
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
