[
https://issues.apache.org/jira/browse/HDFS-10687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805313#comment-16805313
]
Fengnan Li commented on HDFS-10687:
-----------------------------------
[~jakace] [~elgoiri] I am trying to understand the EXPIRE process in
MembershipState in router and please correct me if I am understanding wrong.
* MembershipState and RouterState seem always using caching through
CachedRecordStore and loading their data from the actual StateStoreDriver.
* StateStoreDriver doesn't actually run threads directly to update the state
of membership to EXPIRE, instead, it relies on when the loadCache is called,
the caching will check the expiration and update the state store.
Thanks!
> Federation Membership State Store internal API
> ----------------------------------------------
>
> Key: HDFS-10687
> URL: https://issues.apache.org/jira/browse/HDFS-10687
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Reporter: Íñigo Goiri
> Assignee: Jason Kace
> Priority: Major
> Fix For: 2.9.0, 3.0.0
>
> Attachments: HDFS-10467-HDFS-10687-001.patch,
> HDFS-10687-HDFS-10467-002.patch, HDFS-10687-HDFS-10467-003.patch,
> HDFS-10687-HDFS-10467-004.patch, HDFS-10687-HDFS-10467-005.patch,
> HDFS-10687-HDFS-10467-006.patch, HDFS-10687-HDFS-10467-007.patch,
> HDFS-10687-HDFS-10467-008.patch
>
>
> The Federation Membership State encapsulates the information about the
> Namenodes of each sub-cluster that are participating in Federation. The
> information includes addresses for RPC, Web. This information is stored in
> the State Store and later used by the Router to find data in the federation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
