[
https://issues.apache.org/jira/browse/HIVE-26962?focusedWorklogId=847339&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-847339
]
ASF GitHub Bot logged work on HIVE-26962:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Feb/23 00:46
Start Date: 24/Feb/23 00:46
Worklog Time Spent: 10m
Work Description: pudidic merged PR #4016:
URL: https://github.com/apache/hive/pull/4016
Issue Time Tracking
-------------------
Worklog Id: (was: 847339)
Time Spent: 1h 40m (was: 1.5h)
> 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
> Labels: pull-request-available
> Time Spent: 1h 40m
> 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)
