[jira] [Updated] (KUDU-1364) By default, java client only caches tablet locations for 5 seconds of inactivity

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated KUDU-1364:
-------------------------------------
    Code Review: http://gerrit.cloudera.org:8080/#/c/2449/

> By default, java client only caches tablet locations for 5 seconds of inactivity
> --------------------------------------------------------------------------------
>
>                 Key: KUDU-1364
>                 URL: https://issues.apache.org/jira/browse/KUDU-1364
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.7.0
>            Reporter: Mike Percy
>
> Reported by [~bruceSz] and [~decster].
> When using the Java client, the tablet locations will only be cached for 5 seconds of inactivity before another call to the master is required. This is related to the "socket read timeout" parameter.
> Per Binglin:
> this was "annoying" issue we experienced too :) actually I think it should handle this timeout as normal case(cause master just kicks out idle connection) should not consider this error(and  invalidate caches)
> Workaround:
> {code}
> client = builder
>        .defaultSocketReadTimeoutMs(xxxx)
>        .build();
> {code}
> From the docs:
> {code}org.kududb.client.AsyncKuduClient.AsyncKuduClientBuilder.defaultSocketReadTimeoutMs(long timeoutMs){code}
> Sets the default timeout to use when waiting on data from a socket. Optional. If not provided, defaults to 5s. A value of 0 disables the timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)