impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Tauber-Marshall (JIRA)" <>
Subject [jira] [Created] (IMPALA-5685) Provide a way to invalidate Kudu clients
Date Wed, 19 Jul 2017 21:32:00 GMT
Thomas Tauber-Marshall created IMPALA-5685:

             Summary: Provide a way to invalidate Kudu clients
                 Key: IMPALA-5685
             Project: IMPALA
          Issue Type: Improvement
          Components: Catalog
    Affects Versions: Impala 2.10.0
            Reporter: Thomas Tauber-Marshall

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')

This message was sent by Atlassian JIRA

View raw message