[jira] [Resolved] (IMPALA-5685) Provide a way to invalidate Kudu clients

["Tim Armstrong (Jira)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-5685.
-----------------------------------
    Resolution: Won't Fix

It looks like this has been stable for a while, so will close.

> Provide a way to invalidate Kudu clients
> ----------------------------------------
>
>                 Key: IMPALA-5685
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5685
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Clients
>    Affects Versions: Impala 2.9.0, Impala 2.10.0
>            Reporter: Thomas Tauber-Marshall
>            Priority: Major
>              Labels: kudu
>
> A recent change (IMPALA-5167) moved us from a model where we created a new Kudu client for every Kudu operation to one where we reuse only a single client for each Kudu master(s) that we connect to.
> If something goes wrong with the Kudu client (eg. an auth token expires and isn't refreshed), there's no way to remove the client and create a new one, short of restarting the impalad.
> We don't expect this to happen, as the Kudu team has addressed all of the known issues that would prevent long lived Kudu clients from functioning correctly, but it would be nice if we provided some way of fixing it if it does (eg. something similar to 'invalidate metadata')
> *TODO*: After resolving this, please re-enable the disabled tests in testdata/workloads/functional-query/queries/QueryTest/kudu-timeouts-catalogd.test and kudu-timeouts-impalad.test



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org