accumulo-notifications mailing list archives

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


Adam Fuchs commented on ACCUMULO-1141:

As I understand it, the point of limiting the frame size is to prevent excessive memory allocation
by Thrift, perhaps in the case of a DOS attempt. A single message fits into one frame, and
the size is sent ahead of time (first 4 bytes) to make sure that the message is fully read
from the transport before being executed.
> TServerUtils.startHsHaServer eats maxMessageSize parameter
> ----------------------------------------------------------
>                 Key: ACCUMULO-1141
>                 URL:
>             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
> 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:

View raw message