Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.8.0
-
None
Description
Allowing metastore cache to be initialized asynchronously can be very fragile and should be recommended against. We should either
1. Make it strictly synchronous
2. Or add more testing around async path if there is enough request.
If we take route 1, we can get rid of the updateQueue and syncsent in MetaStorePlugin.
Attachments
Issue Links
- relates to
-
SENTRY-1508 MetastorePlugin.java does not handle properly initialization failure
- Resolved