CORE-17391 Add command metadata to registration state so command history can be tracked #1269
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.
This change adds a command history to the registration state so that registration handlers can take appropriate action based on the previously completed stages. The main use case for this at the moment is to handle replays at the p2p level which cause repeat processing of registration commands. Using the previously processed command list, we can determine in a command processor whether a stage has already been processed successfully or not.