Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
2.1.0
-
None
-
None
Description
Currently HMSFollower proactively checks if sentry is out of sync with HMS and initiates full snapshot, if needed.
There will be false positives with the current logic if there are gaps in the event-id in the notification log sequence.
This jira is aimed at making that logic robust.
Attachments
Attachments
Issue Links
- depends upon
-
SENTRY-2113 MSentryHmsNotification should also hold the notification hash
- Patch Available
- duplicates
-
SENTRY-2119 HMSFollower may not fetch HMS notifications which are out of order
- Open
- is related to
-
HIVE-16886 HMS log notifications may have duplicated event IDs if multiple HMS are running concurrently
- Closed
- relates to
-
HIVE-18526 Backport HIVE-16886 to Hive 2
- Resolved
-
SENTRY-2119 HMSFollower may not fetch HMS notifications which are out of order
- Open
- requires
-
SENTRY-2106 If Sentry is ahead do not trigger a full snapshot
- Resolved
- links to