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

Posted to issues@hive.apache.org by "Taraka Rama Rao Lethavadla (Jira)" <ji...@apache.org> on 2023/04/13 15:15:00 UTC

[jira] [Created] (HIVE-27260) OOM while retrieving delegation tokens using get_all_token_identifiers call

Taraka Rama Rao Lethavadla created HIVE-27260:
-------------------------------------------------

             Summary: OOM while retrieving delegation tokens using get_all_token_identifiers call
                 Key: HIVE-27260
                 URL: https://issues.apache.org/jira/browse/HIVE-27260
             Project: Hive
          Issue Type: Bug
          Components: Hive, Standalone Metastore
            Reporter: Taraka Rama Rao Lethavadla


*get_all_token_identifiers* is retrieving all the entries in table DELEGATION_TOKENS at once.

In systems where the total number of rows is very high causes OOM in HMS while retrieving all the rows at once.

Can we have batching kind of mechanism while retrieving rows from that table?

How about we add timestamp column to that table so that old entries can be cleaned up manually incase going via cleaner did not help?

Even expiry token removal thread is also using the same api *get_all_token_identifiers* and it becomes difficult for cleaner once the number of rows reaches higher number



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