[HDDS-1044] Client doesn't propogate correct error code to client on out of disk space

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.4.0
• Fix Version/s: 0.4.0
• Component/s: Ozone Client, Ozone Datanode
• Target Version/s: 0.4.0
• Assignee: Yiqun Lin
• Reporter: Mukul Kumar Singh
• Created: 02/Feb/19 19:27
• Updated: 07/Feb/19 04:07
• Resolved: 07/Feb/19 04:07

Description

Ozone Datanode doesn't propagate the correct error to client when the datanode runs out of distk space. In space of throwing out of disk space exception, Container not found exception is thrown to clients.

2019-02-02 18:56:22 INFO  KeyValueHandler:149 - Operation: CreateContainer : Trace ID: 72e5c6cc-e624-4acb-bba7-574e3a98ac90WriteChunk1868fc02742c62c3543022377edc0c5ca_stream_4fdc8750-f0d5-4e17-8e37-6d78552053b0_chunk_1 : Message: Container creation failed, due to disk out of space : Result: DISK_OUT_OF_SPACE
2019-02-02 18:56:22 INFO  HddsDispatcher:149 - Operation: WriteChunk : Trace ID: 72e5c6cc-e624-4acb-bba7-574e3a98ac90WriteChunk1868fc02742c62c3543022377edc0c5ca_stream_4fdc8750-f0d5-4e17-8e37-6d78552053b0_chunk_1 : Message: ContainerID 65 does not exist : Result: CONTAINER_NOT_FOUND