accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2069) ThriftTransportPool too aggressive in closing connections
Date Fri, 03 Jan 2014 01:39:50 GMT


Dave Marion commented on ACCUMULO-2069:

Looking in 1.7.0 as to how/where to fix this. I thought initially about using some exponential
backoff function instead of the 3 seconds, but instead realized that the I/O layer likely
handles this for us (keepalive). Found a Thrift implementation[1] that uses this and sets
the recv and send buffer sizes. Looks like we can just add those options in  org.apache.accumulo.core.util.TTimeoutTransport.
Is that the only place in the client where thrift connections are created? What about server


> ThriftTransportPool too aggressive in closing connections
> ---------------------------------------------------------
>                 Key: ACCUMULO-2069
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.4
>            Reporter: Dave Marion
>             Fix For: 1.7.0
> org.apache.accumulo.core.client.impl.ThriftTransportPool closes unused thrift connections
after 3 seconds of inactivty. This can impact performance by causing tablet server connections
to be constantly torn down and set up. Think of the case where you have a MTBW writer with
a small number of threads and a moderate amount of tservers. Make the timeout configurable.

This message was sent by Atlassian JIRA

View raw message