[
https://issues.apache.org/jira/browse/HBASE-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567931#comment-16567931
]
Jingyun Tian commented on HBASE-20986:
--------------------------------------
[~zghaobac] AsyncFSWALProvider currently only provide WAL, thus I think having
this method should be enough?
{code}
WALUtil.getWALBlockSize(conf, fs, path)
{code}
bq. As I comment on RB, here should use another name, may be isRecoverEdits?
OK, this looks more clearly.
> Separate the config of block size when we do log splitting and write Hlog
> -------------------------------------------------------------------------
>
> Key: HBASE-20986
> URL: https://issues.apache.org/jira/browse/HBASE-20986
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: HBASE-20986.master.001.patch,
> HBASE-20986.master.002.patch, HBASE-20986.master.003.patch
>
>
> Since the block size of recovered edits and hlog are the same right now, if
> we set a large value to block size, name node may not able to assign enough
> space when we do log splitting. But set a large value to hlog block size can
> help reduce the number of region server asking for a new block. Thus I think
> separate the config of block size is necessary.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
