[SENTRY-1874] Do not require quiet HMS when taking initial HMS snapshot

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Sentry
• Labels: sentry-ha
• Assignee: Alex Kolbasov
• Reporter: Alex Kolbasov
• Created: 09/Aug/17 00:40
• Updated: 14/Aug/17 19:15
• Resolved: 14/Aug/17 19:15

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.

Issue Links

• links to: Code Review

Sub-Tasks

• Fake subtask to deal with jenkins issues: Resolved