Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1.0
-
None
-
None
Description
Currently behavior of HMSFollower when HDFS sync disabled is as below.
- Take full snapshot of HMS
- Take the Notification Id from the snapshot created.
- Persist the notification Id to SENTRY_HMS_NOTIFICATION_ID table
- Fetches notifications and process new notifications after that point.
This doesn't make sense. Ideally, I think it should work as below.
- Initially, fetch all the notifications with even-id > 0 and process them.
- Subsequently fetch and process new notifications.
Attachments
Issue Links
- is related to
-
SENTRY-2115 Incorrect behavior of HMsFollower when HDFSSync feature is disabled.
- Resolved