[jira] [Commented] (HBASE-29760) TestIncrementalBackup fails 100% on flaky dashboard

["Duo Zhang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-29760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044711#comment-18044711 ] 

Duo Zhang commented on HBASE-29760:
-----------------------------------

Run it locally, it failed with

{noformat}
2025-12-13T00:04:06,651 ERROR [LocalJobRunner Map Task Executor #0 {}] snapshot.ExportSnapshot$ExportMapper(428): Error copying hdfs://localhost:36529/user/zhangduo/test-data/0a15730d-a6e0-ee08-62d0-1331c6e6e39c/data/default/test-1765555285769/69b974a0e2ee574a9c48ea934c8d337f/f/feb68d2a2104418db23d773babeab1b2 to file:/home/zhangduo/hbase/code/hbase-backup/target/test-data/dca8d698-710e-f01c-7399-48db4a53e3ba/backupTarget/backup_1765555437579/default/test-1765555285769/archive/data/default/test-1765555285769/69b974a0e2ee574a9c48ea934c8d337f/f/feb68d2a2104418db23d773babeab1b2
java.io.IOException: Checksum mismatch between hdfs://localhost:36529/user/zhangduo/test-data/0a15730d-a6e0-ee08-62d0-1331c6e6e39c/data/default/test-1765555285769/69b974a0e2ee574a9c48ea934c8d337f/f/feb68d2a2104418db23d773babeab1b2 and file:/home/zhangduo/hbase/code/hbase-backup/target/test-data/dca8d698-710e-f01c-7399-48db4a53e3ba/backupTarget/backup_1765555437579/default/test-1765555285769/archive/data/default/test-1765555285769/69b974a0e2ee574a9c48ea934c8d337f/f/feb68d2a2104418db23d773babeab1b2. Input and output filesystems are of different types.
Their checksum algorithms may be incompatible. You can choose file-level checksum validation via -Ddfs.checksum.combine.mode=COMPOSITE_CRC when block-sizes or filesystems are different.
 Or you can skip checksum-checks altogether with -no-checksum-verify, for the table backup scenario, you should use -i option to skip checksum-checks.
 (NOTE: By skipping checksums, one runs the risk of masking data-corruption during file-transfer.)

        at org.apache.hadoop.hbase.snapshot.ExportSnapshot$ExportMapper.verifyCopyResult(ExportSnapshot.java:676) ~[hbase-mapreduce-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
        at org.apache.hadoop.hbase.snapshot.ExportSnapshot$ExportMapper.copyFile(ExportSnapshot.java:414) ~[hbase-mapreduce-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
        at org.apache.hadoop.hbase.snapshot.ExportSnapshot$ExportMapper.map(ExportSnapshot.java:329) ~[hbase-mapreduce-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
        at org.apache.hadoop.hbase.snapshot.ExportSnapshot$ExportMapper.map(ExportSnapshot.java:253) ~[hbase-mapreduce-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
        at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:145) ~[hadoop-mapreduce-client-core-3.4.2.jar:?]
        at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:800) ~[hadoop-mapreduce-client-core-3.4.2.jar:?]
        at org.apache.hadoop.mapred.MapTask.run(MapTask.java:348) ~[hadoop-mapreduce-client-core-3.4.2.jar:?]
        at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:271) ~[hadoop-mapreduce-client-common-3.4.2.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
        at java.lang.Thread.run(Thread.java:840) ~[?:?]
{noformat}

Seems to be broken by HBASE-28625?

> TestIncrementalBackup fails 100% on flaky dashboard
> ---------------------------------------------------
>
>                 Key: HBASE-29760
>                 URL: https://issues.apache.org/jira/browse/HBASE-29760
>             Project: HBase
>          Issue Type: Bug
>          Components: backup&restore
>            Reporter: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-beta-2
>
>
> It is there for a very long time, I think we need to fix it before making the 3.0.0 release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)