Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.23.2, 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha
-
None
-
Reviewed
Description
Using distcp with '-skipcrccheck' still seems to cause CRC checksums to happen.
Ran into this while debugging an issue associated with source and destination having different blocksizes, and not using the preserve blocksize parameter (-pb). In both 23.1 and 23.2 builds, trying to bypass the checksum verification by using the '-skipcrcrcheck' parameter had no effect, the distcp still failed on checksum errors.
Test scenario to reproduce;
do not use '-pb' and try a distcp from 20.205 (default blksize=128M) to .23 (default blksize=256M), the distcp fails on checksum errors, which is expected due to checksum calculation (tiered aggregation of all blks). Trying the same distcp only providing '-skipcrccheck' still fails with the same checksum error, it is expected that checksum would now be bypassed and the distcp would proceed.
Attachments
Attachments
Issue Links
- is related to
-
HDFS-3889 distcp overwrites files even when there are missing checksums
- Open
-
MAPREDUCE-4654 TestDistCp is @ignored
- Closed
-
HADOOP-8060 Add a capability to discover and set checksum types per file.
- Closed