Adds the bookie cookie query service for http api #4693
+130
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Descriptions of the changes in this PR:
Motivation
When bookie A is decommissioned, the user cannot know whether the decommissioning process is complete. Considering that bookie cookies are deleted after decommissioning, the user can determine whether decommissioning is complete by checking if bookie A's cookies still exist.
The shell admin provides a GetCookieCommand to query cookies for a specified bookie_id, and the HTTP admin also needs to provide an API to query cookies for a specified bookie_id.
Changes
Adds an API to get the cookie of bookie at /api/v1/bookie/cookie.