accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fuchs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1141) TServerUtils.startHsHaServer eats maxMessageSize parameter
Date Mon, 04 Mar 2013 03:49:12 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591972#comment-13591972
] 

Adam Fuchs commented on ACCUMULO-1141:
--------------------------------------

Looks like the TFramedTransport used to have a default max size of 2G, and it was decreased
to 16M in thrift version 0.9.
                
> 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

Mime
View raw message