[
https://issues.apache.org/jira/browse/HBASE-14951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047616#comment-15047616
]
Enis Soztutar commented on HBASE-14951:
---------------------------------------
Just some numbers for comparison
|| heap || memstore perc || maxLogs ||
| 1G | 40% | 8 |
| 2G | 40% | 16 |
| 10G | 40% | 80 |
| 20G | 40% | 160 |
| 32G | 40% | 256 |
Do we need to do {{max(32, calculateMaxLogFiles(..))}} given that with 1G
default it is 8 now?
There is some discrepancy between the memstore size of edits and the WAL size
of the edits, but 2x multiplier I guess accounts for that.
> Make hbase.regionserver.maxlogs obsolete
> ----------------------------------------
>
> Key: HBASE-14951
> URL: https://issues.apache.org/jira/browse/HBASE-14951
> Project: HBase
> Issue Type: Improvement
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-14951-v1.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)
