You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/01/02 23:41:50 UTC

[jira] [Commented] (ACCUMULO-2069) ThriftTransportPool too aggressive in closing connections

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

Keith Turner commented on ACCUMULO-2069:
----------------------------------------

I just noticed that ThriftTransportPool has a public method setIdleTime() which could be used to increase this timeout as a workaround.   It seems like its been there since 1.4.0.

> ThriftTransportPool too aggressive in closing connections
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-2069
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2069
>             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
(v6.1.5#6160)