[
https://issues.apache.org/jira/browse/HIVE-26962?focusedWorklogId=843650&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-843650
]
ASF GitHub Bot logged work on HIVE-26962:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Feb/23 13:14
Start Date: 05/Feb/23 13:14
Worklog Time Spent: 10m
Work Description: 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.
Issue Time Tracking
-------------------
Worklog Id: (was: 843650)
Remaining Estimate: 0h
Time Spent: 10m
> Expose resume/reset ready state through replication metrics when first cycle
> of resume/reset completes
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-26962
> URL: https://issues.apache.org/jira/browse/HIVE-26962
> Project: Hive
> Issue Type: Task
> Reporter: Shreenidhi
> Assignee: Shreenidhi
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As resume/reset workflow also follows optimised bootstrap, so here we have 2
> cycles to mark this flow as complete.
> 1. 1st cycle will be triggered by orchestrator just when resume/reset action
> initiated.
> 2. 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.
> * Once orchestrator sees the RESET_READY state, it will trigger another
> cycle and does necessary work which needs to be done to complete RESET
> workflow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
