You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Shohei Okumiya (Jira)" <ji...@apache.org> on 2025/04/14 06:08:00 UTC

[jira] [Resolved] (HIVE-19785) Race condition when timeout task is invoked during SASL negotation

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

Shohei Okumiya resolved HIVE-19785.
-----------------------------------
    Fix Version/s: NA
       Resolution: Won't Fix

We have discontinued Hive on Spark and EoLed Hive 3. HIVE-26134

> Race condition when timeout task is invoked during SASL negotation
> ------------------------------------------------------------------
>
>                 Key: HIVE-19785
>                 URL: https://issues.apache.org/jira/browse/HIVE-19785
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Sahil Takiar
>            Assignee: Aihua Xu
>            Priority: Major
>             Fix For: NA
>
>
> There is a race condition that leads to some extraneous exception messages when the timeout task is invoked in {{RpcServer}}.
> If a timeout is triggered by {{RpcServer#registerClient}} the method will remove the {{clientId}} from {{pendingClients}}. However, if the SASL negotiation is in progress when the timeout task is invoked, then {{SaslServerHandler#update}} will throw an {{IllegalArgumentException}} complaining that it can't find the {{clientId}} in the map of {{pendingClients}}.
> The timeout still succeeds, but the logging is confusing and multiple exceptions make this difficult to debug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)