Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-5468

REFRESH and a very large table run after catalog restart cannot be cancelled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Impala 2.8.0
    • None
    • Catalog
    • None
    • ghx-label-7

    Description

      It's not possible to cancel a REFRESH on a very large table which is run immediately after catalog restart.

      This can be reproduced by creating a very large table in terms of metadata like say for eg. 4 million files with default 128 MB block size and each file of size 500MB.
      Trying to cancel refresh on this table that is run immediately after catalog restart does not succeed and the only way to stop this refresh is to restart the specific coordinator.

      Please make it possible to cancel long running refreshes without having to restart coordinator.

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. IMPALA-8937 Fine grained table metadata loading on Catalog server

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              mkempanna Mala Chikka Kempanna
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: