You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/05/02 18:31:00 UTC

[jira] [Updated] (HBASE-20520) Failed effort upping default HDFS blocksize, hbase.regionserver.hlog.blocksize

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

stack updated HBASE-20520:
--------------------------
    Attachment: HBASE-20520.branch-2.0.001.patch

> Failed effort upping default HDFS blocksize, hbase.regionserver.hlog.blocksize
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-20520
>                 URL: https://issues.apache.org/jira/browse/HBASE-20520
>             Project: HBase
>          Issue Type: Sub-task
>          Components: conf
>            Reporter: stack
>            Priority: Major
>         Attachments: HBASE-20520.branch-2.0.001.patch
>
>
> Good one found by our [~mdrob]. Problem in the parent issue where failed attempt doubling default block size but halving the size at which roll -- so we end up in roughly same place only we make less small WALs in those cases where we are writing furiously and fail to roll before starting a new block.
> From Drob: ".../we drop default log roll to 0.5, but we don't actually increase the block size... AbstractProtobufLogWriter.java:164 still uses default HDFS block sizing and AbstractFSWAL.java:408 block size is only used in a log message, never actually makes it to files...". 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)