[
https://issues.apache.org/jira/browse/KUDU-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3648.
---------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
Fixed with KUDU-3646 and KUDU-3647.
> BUF_ERROR in zlib::Uncompress() when processing HMS notification event
> ----------------------------------------------------------------------
>
> Key: KUDU-3648
> URL: https://issues.apache.org/jira/browse/KUDU-3648
> Project: Kudu
> Issue Type: Bug
> Components: hms, master
> Reporter: Alexey Serbin
> Priority: Major
> Labels: catalog, impala-kudu, integration, master
> Fix For: 1.18.0
>
>
> Under certain conditions, HMS notification listener fails to process messages
> in 'gzip(json-2.0)' format, generating warning messages like below. Such a
> situation requires manual intervention to restore consistency between Kudu
> and HMS. For example, in the example below it was necessary to drop Kudu
> tables that hadn't been deleted because of the failure to process
> corresponding HMS notification message.
> {noformat}
> W20250221 15:16:31.617455 2109673 hms_notification_log_listener.cc:293]
> Failed to handle Hive Metastore notification: 2977151 DROP_TABLE table_name:
> Runtime error: failed decompress message: zlib error: BUF_ERROR
> {noformat}
> There were reports of this issue manifesting itself when running {{DROP
> DATABASE <database_name> CASCADE}} from impala-shell. There was no error
> triggered at Impala side (that's due to the design of the Kudu-HMS
> integration), but it was necessary to manually drop corresponding Kudu tables.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
