You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2024/11/14 09:26:00 UTC
[jira] [Resolved] (HBASE-28268) Provide option to skip wal while using TableOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-28268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani resolved HBASE-28268.
----------------------------------
Fix Version/s: 3.0.0-beta-2
Hadoop Flags: Reviewed
Resolution: Fixed
> Provide option to skip wal while using TableOutputFormat
> --------------------------------------------------------
>
> Key: HBASE-28268
> URL: https://issues.apache.org/jira/browse/HBASE-28268
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Ujjawal Kumar
> Assignee: Raghavendra B
> Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> If we have replication setup between clusters A <-> B, during production incidents where HFiles get corrupted (e.g. via hdfs missing blocks) on cluster A, we can use CopyTable job to copy the data from B
> In those cases considering the data is being copied from B to A via CopyTable, it doesn't make sense to write to WALs on A using TableOutputFormat (since the mutations being copied already exist on B).
> We can add a config to customise durability ([https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Durability.java]) within TableOutputFormat so that an operator can use it to skip WAL writes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)