[
https://issues.apache.org/jira/browse/HIVE-26930?focusedWorklogId=856715&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-856715
]
ASF GitHub Bot logged work on HIVE-26930:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Apr/23 10:40
Start Date: 13/Apr/23 10:40
Worklog Time Spent: 10m
Work Description: subhasisgorai opened a new pull request, #4230:
URL: https://github.com/apache/hive/pull/4230
What changes does this PR contain?
To support the Planned/Unplanned Failover, we need the capability to
increase the retention period for both the Notification Logs and Change Manager
entries until the successful reverse replication is done (i.e. the Optimized
Bootstrap). A database-level property 'repl.db.under.failover.sync.pending' was
introduced to signify this state. This PR contains the changes for,
1. selective deletion of notification events that are not relevant to the
database(s) in failover
2. skipping the CM clearer thread execution until the time the Optimized
Bootstrap is not done
Why this change is needed?
The change is needed to make the Optimized Bootstrap and Point-in-time
consistency possible. If the relevant Notification logs and Change Manager
entries are not retained, we can't perform the Optimized Bootstrap.
Were the changes tested?
I have included relevant unit tests in this PR, and will also perform manual
verification after deploying the changes on a cluster.
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description, screenshot and/or a reproducable
example to show the behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Hive versions or within the unreleased branches such as master.
If no, write 'No'.
-->
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
-->
Issue Time Tracking
-------------------
Worklog Id: (was: 856715)
Remaining Estimate: 0h
Time Spent: 10m
> Support for increased retention of Notification Logs and Change Manager
> entries
> -------------------------------------------------------------------------------
>
> Key: HIVE-26930
> URL: https://issues.apache.org/jira/browse/HIVE-26930
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Subhasis Gorai
> Assignee: Subhasis Gorai
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to support the Planned/Unplanned Failover use cases, we need the
> capability to increase the retention period for both the Notification Logs
> and Change Manager entries until the successful reverse replication is done
> (i.e. the Optimized Bootstrap).
> If the relevant Notification logs and Change Manager entries are not
> retained, we can't perform a successful Optimized Bootstrap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
