[
https://issues.apache.org/jira/browse/ACCUMULO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592785#comment-13592785
]
Josh Elser commented on ACCUMULO-1141:
--------------------------------------
I'm curious, what were the performance effects you saw with changing the frame
size?
> TServerUtils.startHsHaServer eats maxMessageSize parameter
> ----------------------------------------------------------
>
> Key: ACCUMULO-1141
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1141
> Project: Accumulo
> Issue Type: Bug
> Components: thrift, tserver
> Reporter: Adam Fuchs
> Assignee: Eric Newton
> Priority: Blocker
> Fix For: 1.5.0
>
> Attachments: ACCUMULO-1141.patch
>
>
> org.apache.accumulo.server.util.TServerUtils.startHsHaServer doesn't do
> anything with the maxMessageSize parameter, causing the maximum frame size to
> be about 16MB. This is too small for many mutations, and would greatly
> restrict the values that are commonly used with Accumulo.
> To fix, we need to include a frame size parameter in the
> TFramedTransport.Factory returned by
> org.apache.accumulo.core.util.ThriftUtil.transportFactory().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
