Siyao Meng created HDDS-11760:
---------------------------------
Summary: Print more detail on Ratis send request ERROR
Key: HDDS-11760
URL: https://issues.apache.org/jira/browse/HDDS-11760
Project: Apache Ozone
Issue Type: Task
Reporter: Siyao Meng
Assignee: Siyao Meng
Currently Ozone client doesn't give any detail on Ratis send request failure
with default logging level:
{code:java}
[2024-10-28 15:05:08,874] ERROR [dea_ofs_sink_test_v1|task-0] Failed to send
request, message=null (org.apache.ratis.client.impl.OrderedAsync:175)
[2024-10-28 15:05:09,006] ERROR [dea_ofs_sink_test_v1|task-0] Failed to send
request, message=cmdType: WriteChunk
[2024-10-28 15:05:09,007] ERROR [dea_ofs_sink_test_v1|task-0] Failed to send
request, message=cmdType: WriteChunk
[2024-10-28 15:05:09,008] ERROR [dea_ofs_sink_test_v1|task-0] Failed to send
request, message=cmdType: WriteChunk
[2024-10-28 15:05:09,009] ERROR [dea_ofs_sink_test_v1|task-0] Failed to send
request, message=cmdType: PutBlock
[2024-10-28 15:05:09,022] WARN [dea_ofs_sink_test_v1|task-0] Encountered
exception java.io.IOException: Unexpected Storage Container Exception:
java.util.concurrent.CompletionException: Failed to write chunk
113750153632180233_chunk_1 into block conID: 78079 locID: 113750153632180233
bcsId: 0 on the pipeline Pipeline[ Id: ....{code}
It should print at least why it failed when it ERRORed out. Only when DEBUG
logging is enabled will it print the stacktrace. e.g. in the case above it
leads to HDDS-11257:
{code:java}
Caused by: java.lang.NoClassDefFoundError:
org/apache/ratis/thirdparty/io/netty/handler/proxy/HttpProxyHandler {code}
This prevents us devs from debugging the issue efficiently. I will make a
change in Ozone/Ratis client to print the details / stacktrace when ERROR has
occurred.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]