JackieTien97 opened a new pull request, #18415:
URL: https://github.com/apache/iotdb/pull/18415
## Description
This PR reduces excessive WARN log output when query execution fails for
expected reasons.
- Classify expected query exceptions in `AbstractDriverThread`, following
the behavior on `master`.
- Do not emit `[ExecuteFailed]` WARN stack traces for memory exhaustion,
IoTDB business exceptions, or date parsing errors.
- Preserve WARN stack traces for unexpected internal errors and log their
root causes.
- Replace the complete TVList `dataTypes` list in memory-reservation
warnings with `dataTypeCount`.
- Add unit tests for exception classification and abort-cause mapping.
## Root cause
`ResourceByPathUtils` printed every data type in an aligned TVList. A
5,000-column aligned series therefore generated a warning of roughly 35 KB for
each memory-reservation failure. The same expected failure was then caught by
`AbstractDriverThread`, which emitted another `[ExecuteFailed]` WARN with a
full stack trace.
Under sustained memory pressure, these duplicate and oversized records
caused the DataNode WARN log to grow rapidly and added avoidable logging and
allocation overhead.
## Impact
Known query failures are still propagated to the query through the existing
1.3 abort-cause interface. The concise TVList memory warning remains available
for diagnosis, while duplicate stack traces and unbounded column-list output
are removed. Unexpected exceptions continue to produce WARN stack traces.
## Tests
```shell
./mvnw -pl iotdb-core/datanode -am \
-Dtest=AbstractDriverThreadTest \
-DfailIfNoTests=false \
-Dsurefire.failIfNoSpecifiedTests=false test
```
Result: 2 tests passed; reactor build succeeded.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
