Details
-
Sub-task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.0.0
-
None
Description
Now HMSFollower has been initialized at the constructor of SentryService. It would be better to initialize it when the service starts, e.g runServer().
Attachments
Attachments
Issue Links
- blocks
-
SENTRY-1717 Sentry should emit log messages when it is ready to serve requests.
- Resolved
- breaks
-
SENTRY-1757 Avoid using local hive meta store with wrong configuration
- Resolved
- is duplicated by
-
SENTRY-1722 Create HMSFollower when SentryService.Start() is called
- Resolved
- is related to
-
SENTRY-1669 HMSFollower should read current processed notification ID from database every time it runs
- Resolved
-
SENTRY-1713 Enable TestHDFSIntegrationEnd2End.testEnd2End
- Resolved
-
SENTRY-1722 Create HMSFollower when SentryService.Start() is called
- Resolved
-
SENTRY-1747 HMSFollower shouldn't create local hive during tests
- Resolved
- relates to
-
SENTRY-1723 HDFS e2e tests should wait for HMSFollower to start
- Resolved
-
SENTRY-1712 Add trigger mechanism for Sentry to push full path snapshot to Name Node
- Resolved
- links to