You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Shreenidhi (Jira)" <ji...@apache.org> on 2023/01/18 07:27:00 UTC

[jira] [Assigned] (HIVE-26962) Expose resume/reset ready state through replication metrics when first cycle of resume/reset completes

     [ https://issues.apache.org/jira/browse/HIVE-26962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shreenidhi reassigned HIVE-26962:
---------------------------------

    Assignee: Shreenidhi

> 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
>
> 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 the 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)