[
https://issues.apache.org/jira/browse/HBASE-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-17048:
-------------------------------------------
Attachment: HBASE-17012_3.patch
Updated patch that initializes to 4K and increments the size in powers of 2
(exponentially).
There are other allocations we do for header, encrypted buffer etc. But those
are not going thro the new MaxByteBufAllocator. Is that fine?
Currently the limit is 128 * 1024 * 1024. Should we reduce the limit?
[~Apache9]
What do you think?
> Introduce a helper class to calcuate suitable ByteBuf size when allocating
> send buffer in FanOutOneBlockAsyncDFSOutputHelper
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-17048
> URL: https://issues.apache.org/jira/browse/HBASE-17048
> Project: HBase
> Issue Type: Sub-task
> Components: wal
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-17012_3.patch, HBASE-17048.patch
>
>
> As [~ram_krish] mentioned in HBASE-17021
> https://issues.apache.org/jira/browse/HBASE-17021?focusedCommentId=15646938&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15646938
> The default ByteBuf size is 256B which is too small.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
