[HDDS-5989] Binary content printed for failed chunk write

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: Ozone Client
• Labels: pull-request-available
• Target Version/s: 1.3.0
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 15/Nov/21 14:54
• Updated: 29/Nov/21 10:57
• Resolved: 29/Nov/21 09:40

Description

When write chunk command fails, the exception thrown includes binary data in the message:

java.io.IOException: Failed to execute command cmdType: WriteChunk
containerID: 1
datanodeUuid: "4aa35961-c206-4fa0-b9fe-cb5f2bafa5b5"
writeChunk {
  blockID {
    containerID: 1
    localID: 18
    blockCommitSequenceId: 96618
  }
  chunkData {
    chunkName: "dq9c8amgzt_testdata_chunk_96618"
    offset: 5064622080
    len: 1048576
    checksumData {
      type: CRC32
      bytesPerChecksum: 1048576
      checksums: "R\205\335\331"
    }
  }
  data: "/OMxtNJH{gG8[\":w{5OAHd@Y7V6HW\"p> .... <more binary content here>"
}

Issue Links

• links to: GitHub Pull Request #2846