[
https://issues.apache.org/jira/browse/HBASE-14951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068384#comment-15068384
]
stack commented on HBASE-14951:
-------------------------------
So, default now is 256 when before it was 32: i.e. usual heap size is 31G or
so... and the default max WALs was 32 but with this algorithm, we get a max of
256 instead. Need to highlight this difference when we roll out 1.2 [~busbey].
Can you explain the *2 in the release note [~vrodionov] *2 seems a bit
arbitrary no? And if it is to stop blocking because too many WALs, is that
going to happen now with these new limits?
> Make hbase.regionserver.maxlogs obsolete
> ----------------------------------------
>
> Key: HBASE-14951
> URL: https://issues.apache.org/jira/browse/HBASE-14951
> Project: HBase
> Issue Type: Improvement
> Components: Performance, wal
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14951-v1.patch, HBASE-14951-v2.patch
>
>
> There was a discussion in HBASE-14388 related to maximum number of log files.
> It was an agreement that we should calculate this number in a code but still
> need to honor user's setting.
> Maximum number of log files now is calculated as following:
> maxLogs = HEAP_SIZE * memstoreRatio * 2/ LogRollSize
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
