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

Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2021/01/02 19:51:00 UTC

[jira] [Commented] (HBASE-25431) MAX_FILESIZE and MEMSTORE_FLUSHSIZE should not be set negative number

    [ https://issues.apache.org/jira/browse/HBASE-25431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257497#comment-17257497 ] 

Michael Stack commented on HBASE-25431:
---------------------------------------

So if < 0, we set it to maxFileSizeLowerLimit (2MB) instead?

> MAX_FILESIZE and MEMSTORE_FLUSHSIZE should not be set negative number
> ---------------------------------------------------------------------
>
>                 Key: HBASE-25431
>                 URL: https://issues.apache.org/jira/browse/HBASE-25431
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha-1, 2.4.0
>            Reporter: Baiqiang Zhao
>            Assignee: Baiqiang Zhao
>            Priority: Major
>         Attachments: image-2020-12-22-11-46-38-967.png
>
>
> MAX_FILESIZE and MEMSTORE_FLUSHSIZE will judge whether it's value <= 0 in flush and split logic, if true, change to default value. We should check this in TableDescriptorChecker
> !image-2020-12-22-11-46-38-967.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)