Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
  3. SENTRY-1539

HMS Follower should store arriving HMS notifications

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 2.0.0
    • 2.0.0
    • Sentry

    • HMS Follower should save arriving HMS notifications in the DB.

    Description

      Once HMS receives a notification from HMS it should store in in Sentry DB. The addition of the notification event should be bundled in the same transaction that handles the event, so the whole event is either processed or not.

      Attachments

        Issue Links

          duplicates

          Sub-task - The sub-task of the issue SENTRY-1587 Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

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

          Sub-task - The sub-task of the issue SENTRY-1536 Refactor SentryStore transaction management to allow for extra TransanctionBlocks for a single permission update

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue SENTRY-1538 Create schema for storing HMS path change and Sentry permission change.

          • Major - Major loss of function.
          • Resolved
          is related to

          Sub-task - The sub-task of the issue SENTRY-1675 sentry-hdfs-dist should include sentry-core-common after refactor SentryHDFSServiceClientDefaultImpl

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              hahao Hao Hao
              akolb Alex Kolbasov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: