[
https://issues.apache.org/jira/browse/HDFS-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Virajith Jalaparti updated HDFS-12713:
--------------------------------------
Attachment: HDFS-12713-HDFS-9806.003.patch
Posting patch v3 that builds on v2, rebases it on the current branch, fixes
{{TextFileRegionAliasMap}} and {{InMemoryLevelDBAliasMapClient}} to ensure that
the block pool id parameter in {{getReader}} and {{getWriter}} is handled
correctly.
[~ehiggs], one issue that came up when running
{{TestNameNodeProvidedImplementation.testInMemoryAliasMap}} with v2, is that
when the Datanodes try to load blocks (in
{{ProvidedBlockPoolSlice.fetchVolumeMap}}) using
{{InMemoryLevelDBAliasMapClient}}, the request to the Namenode might fail. As a
result, the datanodes do not start up. Retrying helps. As a temporary fix, I
added a simple retry logic in {{ProvidedBlockPoolSlice.fetchVolumeMap}} in v3.
We need a more permanent fix for this issue. I think this should be done in a
separate JIRA.
> [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,
> HDFS-12713-HDFS-9806.002.patch, HDFS-12713-HDFS-9806.003.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]
