[
https://issues.apache.org/jira/browse/HBASE-28987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933987#comment-17933987
]
Andor Molnar commented on HBASE-28987:
--------------------------------------
[~zhangduo]
We don't actually introduce another pointer to manage, but separating the
in-memory pointer from the persisted one.
Please take a look at this
[patch|https://github.com/apache/hbase/pull/6633/files#diff-7988a9d050fc7e65cf11bd0e1d3b9d466b95fd9ec599075f022e73579a917a1f].
Here we introduced a 3-state return value for the {{replicate()}} method where
the original behaviour was handled by COMMITTED (true) and FAILED (false)
values. The only difference is that we skip persisting the pointer if
{{replicate()}} returns with SUBMITTED which is only used by the new continuous
backup endpoint.
I think this is already simple enough and safe in terms of backward
compatibility, because actually the original logic has not been touched. Above
2 solutions proposed by you seems more error-prone to me.
> Developing a Custom ReplicationEndpoint to Support External Storage
> Integration
> -------------------------------------------------------------------------------
>
> Key: HBASE-28987
> URL: https://issues.apache.org/jira/browse/HBASE-28987
> Project: HBase
> Issue Type: Task
> Components: backup&restore
> Affects Versions: 2.6.0, 3.0.0-alpha-4
> Reporter: Vinayak Hegde
> Assignee: Vinayak Hegde
> Priority: Major
>
> *Develop a Custom Replication Endpoint*
> Implement a custom replication endpoint to support the backup of WALs to
> external storage systems, such as HDFS-compliant storages (including HDFS,
> S3, ADLS, and GCS via respective Hadoop connectors).
> *Support for Bulk-loaded Files*
> Add functionality to back up bulk-loaded files in addition to regular WALs.
> *Ensure Process Durability*
> Ensure the backup process is durable, with no WALs being missed, even in the
> event of issues in the cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
