[
https://issues.apache.org/jira/browse/HIVE-24946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391950#comment-17391950
]
Pravin Sinha commented on HIVE-24946:
-------------------------------------
+1, LGTM
> Handle failover case during Repl Load
> -------------------------------------
>
> Key: HIVE-24946
> URL: https://issues.apache.org/jira/browse/HIVE-24946
> Project: Hive
> Issue Type: New Feature
> Reporter: Haymant Mangla
> Assignee: Haymant Mangla
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> To handle:
> # Introduce two states of failover db property to denote nature of database
> at the time failover was initiated.
> # If failover start config is enabled and dump directory contains failover
> marker file, then in incremental load as a preAckTask, we should
> ## Remove repl.target.for from target db.
> ## Set repl.failover.endpoint = "TARGET"
> ## Updated the replication metrics saying that target cluster is failover
> ready
> # In the first dump operation in reverse direction, presence of failover
> ready marker and repl.failover.endpoint = "TARGET" will be used as indicator
> for bootstrap iteration.
> # In any dump operation except the first dump operation in reverse dxn, if
> repl.failover.endpoint is set for db and failover start config is set to
> false, then remove this property.
> # In incremental load, if the failover start config is disabled, then add
> repl.target.for and remove repl.failover.endpoint if present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
