[HBASE-27542] Remove unneeded distcp log cleanup after incremental backups

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-3
• Fix Version/s: 2.6.0, 3.0.0-alpha-4
• Component/s: backup&restore
• Assignee: Jarryd Lee
• Reporter: Jarryd Lee
• Created: 21/Dec/22 01:07
• Updated: 25/Jan/23 05:51
• Resolved: 24/Jan/23 13:39

Description

During the completion step of incremental backups, the TableBackupClient ensures distcp logs are cleaned up. However, DistCp already ensures that the metafolder, where the distcp logs are stored, is cleaned up via the CopyCommitter.

Additionally, when running in an external yarn cluster external to hbase, this causes issues as it assumes a common filesystem.

The TableBackupClient cleanup method should be able to be safely removed.

e: After digging in to this even more, the `_distcp_log` path used in the `TableBackupClient` is not actually the correct path used by distcp.

Issue Links

• blocks: HBASE-27541 Backups should be able to be restored to a separate filesystem
• links to: GitHub Pull Request #4934
• links to: GitHub Pull Request #4934