Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-7954 Support automatic invalidates using metastore notification events
  3. IMPALA-8240

Event processor should keep trying if metastore is unavailable

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • Impala 3.2.0
    • None
    • None
    • ghx-label-7

    Description

      Currently, if metastore is restarted (or is unresponsive), event processor throws MetastoreFetchNotificationException and changes its state to ERROR state. Event processor does not get restarted until either a reset() is called or catalogd is restarted. Event processor should keep polling for new events so that things will automatically start working when metastore is back up.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-12561 Event-processor shouldn't go into ERROR state for failures in fetching events

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              anuragmantri Anurag Mantripragada
              vihangk1 Vihang Karajgaonkar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: