[
https://issues.apache.org/jira/browse/HBASE-28987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934091#comment-17934091
]
Duo Zhang commented on HBASE-28987:
-----------------------------------
Or we can introduce a more general logic, that the replicate method just means
we send the things out, and before persisting, we should make sure that all the
edits which are sent out should be committed, if there are any errors while
committing, we throw a special exception and let the replication restart from
the previous position.
In this way, we do not need to introduce a special replication position track
logic for S# backup. For the old implementation, for now we just need to do
nothing before persisting, but in the future there are also rooms to
improvement the performance.
What do you guys think?
Thanks.
> 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)
