You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 18:58:00 UTC

[jira] [Resolved] (HBASE-6490) 'dfs.client.block.write.retries' value could be increased in HBase

     [ https://issues.apache.org/jira/browse/HBASE-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-6490.
----------------------------------------
    Resolution: Won't Fix

> 'dfs.client.block.write.retries' value could be increased in HBase
> ------------------------------------------------------------------
>
>                 Key: HBASE-6490
>                 URL: https://issues.apache.org/jira/browse/HBASE-6490
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 2.0.0
>         Environment: all
>            Reporter: Nicolas Liochon
>            Priority: Minor
>
> When allocating a new node during writing, hdfs tries 'dfs.client.block.write.retries' times (default 3) to write the block. When it fails, it goes back to the nanenode for a new list, and raises an error if the number of retries is reached. In HBase, if the error is while we're writing a hlog file, it will trigger a region server abort (as hbase does not trust the log anymore). For simple case (new, and as such empty log file), this seems to be ok, and we don't lose data. There could be some complex cases if the error occurs on a hlog file with already multiple blocks written.
> Logs lines are:
> "Exception in createBlockOutputStream", then "Abandoning block " followed by "Excluding datanode " for a retry.
> IOException: "Unable to create new block.", when the number of retries is reached.
> Probability of occurence seems quite low, (number of bad nodes / number of nodes)^(number of retries), and it implies that you have a region server without its datanode. But it's per new block.
> Increasing the default value of 'dfs.client.block.write.retries' could make sense to be better covered in chaotic conditions.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)