[
https://issues.apache.org/jira/browse/SENTRY-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156604#comment-16156604
]
Alexander Kolbasov commented on SENTRY-1918:
--------------------------------------------
I think that it is possible to have much simpler fix for the original problem
that doesn't require any of these changes. The idea is to create a helper
singleton class where parties can register (by name) and say - hey, I am busy,
hey, I am available - using a simple map from name to atomic value. This way we
do not require all these plumbing changes (which may be useful for other
purposes but that's another story).
> NN snapshot should not be served while HMS snapshot is collected
> ----------------------------------------------------------------
>
> Key: SENTRY-1918
> URL: https://issues.apache.org/jira/browse/SENTRY-1918
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Alexander Kolbasov
> Assignee: Brian Towles
> Fix For: 2.0.0
>
> Attachments: SENTRY-1918.002.patch, SENTRY-1918.003.patch,
> SENTRY-1918.004.patch, SENTRY-1918.005.patch, SENTRY-1918.006.patch,
> SENTRY-1918.007.patch, SENTRY-1918.008.patch, SENTRY-1918.009.patch
>
>
> While Sentry collects full HMS snapshot, Namenode still sends requests to
> sentry and may request a full snapshot which is useless because a new one
> will be available shortly. It is important to prevent this from happening so
> that we do not collect two snapshots in memory at the same time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
