[
https://issues.apache.org/jira/browse/HDFS-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246568#comment-16246568
]
Virajith Jalaparti commented on HDFS-12713:
-------------------------------------------
bq. I don't have a clean solution (yet) to handle this in the
InMemoryLevelDBAliasMap since there's no natural way to dispatch to the
appropriate Namenode.
Currently, the only way {{InMemoryLevelDBAliasMapClient}} can understand which
NN it is talking to, is through a configuration parameter. As long as, there is
no support for multiple NNs sharing the same provided volume (which HDFS-9806
does not support anyway), {{InMemoryAliasMapProtocol}} can be modified to have
a {{getBlockPoolID}}. If that needs to be supported,
{{InMemoryLevelDBAliasMapClient}} needs to know how to communicate with
multiple NNs, and this would require some integration with {{BPOfferService}}
and related components.
> [READ] Refactor FileRegion and BlockAliasMap to separate out HDFS metadata
> and PROVIDED storage metadata
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-12713
> URL: https://issues.apache.org/jira/browse/HDFS-12713
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Virajith Jalaparti
> Assignee: Ewan Higgs
> Attachments: HDFS-12713-HDFS-9806.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
