You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/03/10 05:44:41 UTC
[jira] [Resolved] (HBASE-13185) Document
hbase.regionserver.thrift.framed.max_frame_size_in_mb more clearly
[ https://issues.apache.org/jira/browse/HBASE-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-13185.
---------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Daisuke Kobayashi
Hadoop Flags: Reviewed
Pushed. Thank you [~daisuke.kobayashi] Should show next time we roll the doc.
> Document hbase.regionserver.thrift.framed.max_frame_size_in_mb more clearly
> ---------------------------------------------------------------------------
>
> Key: HBASE-13185
> URL: https://issues.apache.org/jira/browse/HBASE-13185
> Project: HBase
> Issue Type: Improvement
> Components: documentation
> Reporter: Daisuke Kobayashi
> Assignee: Daisuke Kobayashi
> Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: HBASE-13185.patch
>
>
> Current document does not make sense how much is it going to allocate for {{hbase.regionserver.thrift.framed.max_frame_size_in_mb}}:
> http://hbase.apache.org/book.html#hbase.regionserver.thrift.framed.max_frame_size_in_mb
> It is 2MB by default per the code, so that it would be fine to document this:
> https://github.com/apache/hbase/blob/master/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java#L450-L451
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)