Uploaded image for project: 'Sentry'
  1. Sentry
  2. SENTRY-1874

Do not require quiet HMS when taking initial HMS snapshot

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: Sentry
    • Labels:

      Description

      When Sentry starts initially, it needs to get a full snapshot from HMS and associate it with a specific notification ID. HMS does not provide any mechanism to get a consistent snapshot with known notification ID. SO Sentry does the following:

      1) Read current notification ID_0
      2) Obtain full snapshot from HMS
      3) Read current notification ID_1
      4) If (ID_0 != ID_1) goto 1.

      This creates a problem that the process may never converge when there is some constant stream of HMS activity affecting notification IDs. We would like to be able to use a problem that can converge in the presence of updates.

        Attachments

        1. SENTRY-1874.02.patch
          53 kB
          Alex Kolbasov

          Issue Links

            Activity

              People

              • Assignee:
                akolb Alex Kolbasov
                Reporter:
                akolb Alex Kolbasov
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: