shreenidhiSaigaonkar opened a new pull request, #4016:
URL: https://github.com/apache/hive/pull/4016
### What changes were proposed in this pull request?
* Exposes 'RESUME_READY' state in replication metrics when first cycle of
resume/reset completes
### Why are the changes needed?
* As resume/reset workflow also follows optimised bootstrap, so here we have
2 cycles to mark this flow as complete.
* 1st cycle will be triggered by orchestrator just when resume/reset
action initiated.
* Now to initiate another cycle orchestrator needs to know if the first
cycle got complete. To do this we need a mechanism in hive where it puts
RESUME/RESET_READY state in replication metrics once the first cycle of
RESUME/RESET completes.
* So the current change put's RESUME_READY status after first cycle of
optimised bootstrap if it finds repl.resume.started flag set to true.
* Once orchestrator sees the RESET_READY state, it will trigger the another
cycle and does necessary work which needs to be done.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
* Added integration test which covers end-to-end flow of RESET/RESUME
replication action.
* Tested the change in local environment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
