Race Condition on Lookup Status Endpoint

After we send a POST request to update a registered lookup, we will get unpredicted result from GET endpoint on lookup status. This could happen when the GET request hits the coordinator too early OR updating the lookup on historicals involves downloading large amount of data from a remote location.

A suggested solution could be blocking GET request before update finishes.

I can work to solve this if the is approved to be an issue.

[leventov]

This might be essentially the same problem as fixed in #4758, just on lookup update rather than initial loading.

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

[github-actions]

This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.