Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.23.2, 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha
    • Fix Version/s: 2.0.2-alpha
    • Component/s: tools
    • Labels:
      None

      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

        1. hdfs-3054.patch
          3 kB
          Rahul Jain
        2. HDFS-3054.004.patch
          3 kB
          Colin P. McCabe
        3. HDFS-3054.002.patch
          3 kB
          Colin P. McCabe

          Issue Links

            Activity

              People

              • Assignee:
                cmccabe Colin P. McCabe
                Reporter:
                patwhitey2007 patrick white
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: