You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/22 09:44:00 UTC
[jira] [Work logged] (HIVE-24918) Handle failover case during Repl
Dump
[ https://issues.apache.org/jira/browse/HIVE-24918?focusedWorklogId=569595&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-569595 ]
ASF GitHub Bot logged work on HIVE-24918:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Mar/21 09:43
Start Date: 22/Mar/21 09:43
Worklog Time Spent: 10m
Work Description: hmangla98 opened a new pull request #2097:
URL: https://github.com/apache/hive/pull/2097
What changes were proposed in this pull request?
Handle failover case during repl dump
Why are the changes needed?
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added three tests in TestReplicationScenariosAcidTables.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 569595)
Remaining Estimate: 0h
Time Spent: 10m
> Handle failover case during Repl Dump
> -------------------------------------
>
> Key: HIVE-24918
> URL: https://issues.apache.org/jira/browse/HIVE-24918
> Project: Hive
> Issue Type: New Feature
> Reporter: Haymant Mangla
> Assignee: Haymant Mangla
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To handle:
> a) Whenever user wants to go ahead with failover, during the next or subsequent repl dump operation upon confirming that there are no pending open transaction events, in should create a _failover_ready marker file in the dump dir.
> b) Skip next repl dump instances once we have the marker file placed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)