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 Thu, 07 Mar 2013 23:14:14 GMT


Adam Fuchs commented on ACCUMULO-1141:

[~elserj]: Mutations over the frame size generated exceptions -- it wasn't so much a performance
problem as it was a stability problem. For us, these exceptions resulted in an infinite loop
of retries. I'm not sure if that was in our code or in the Accumulo client library.
> 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