You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/15 00:28:00 UTC
[jira] [Updated] (HBASE-20686) Asyncfs should retry upon RetryStartFileException
[ https://issues.apache.org/jira/browse/HBASE-20686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell updated HBASE-20686:
----------------------------------------
Affects Version/s: (was: 2.0.0-beta-1)
Assignee: (was: Wei-Chiu Chuang)
Status: Open (was: Patch Available)
> Asyncfs should retry upon RetryStartFileException
> -------------------------------------------------
>
> Key: HBASE-20686
> URL: https://issues.apache.org/jira/browse/HBASE-20686
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient
> Environment: HBase 2.0, Hadoop 3 with at-rest encryption
> Reporter: Wei-Chiu Chuang
> Priority: Major
> Attachments: HBASE-20686.master.001.patch, HBASE-20686.master.002.patch
>
>
> In Hadoop-2.6 and above, HDFS client retries on RetryStartFileException when NameNode experience encryption zone related issue. The code exists in DFSOutputStream#newStreamForCreate(). (HDFS-6970)
> In HBase-2's asyncfs implementation, FanOutOneBlockAsyncDFSOutputHelper#createOutput() is somewhat an imitation of HDFS's DFSOutputStream#newStreamForCreate(). However it does not retry upon RetryStartFileException. So it is less resilient to such issues.
> Also, DFSOutputStream#newStreamForCreate() upwraps RemoteExceptions, but asyncfs does not. Therefore, hbase gets different exceptions than before.
> File this jira to get this corrected.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)