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

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2021/05/23 16:21:00 UTC

[jira] [Created] (KUDU-3287) Threads can linger for some time after calling close on the Java KuduClient

Grant Henke created KUDU-3287:
---------------------------------

             Summary: Threads can linger for some time after calling close on the Java KuduClient
                 Key: KUDU-3287
                 URL: https://issues.apache.org/jira/browse/KUDU-3287
             Project: Kudu
          Issue Type: Bug
    Affects Versions: 1.14.0, 1.13.0, 1.12.0
            Reporter: Grant Henke
            Assignee: Grant Henke


After the upgrade to Netty 4 in Kudu 1.12 the close/shutdown behavior of the Java client changed where threads and resources could linger for some time after the call to close() returned. This looks the be because `bootstrap.config().group().shutdownGracefully` is called with the default of 15s and returns asynchronously. Additionally, the default ExecutorService was not shutdown on close. 



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