[
https://issues.apache.org/jira/browse/FLINK-35587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junrui Li updated FLINK-35587:
------------------------------
Description:
While running TPC-DS 10TB benchmark on the latest master branch locally, I've
encountered a failure in certain queries, specifically query 75, resulting in
the error "The read buffer is null in credit-based input channel".
Using a binary search approach, I identified the offending commit as
FLINK-33668. After reverting FLINK-33668 and subsequent commits, the issue
disappears. Re-applying FLINK-33668 to the branch re-introduces the error.
Please see the attached image for the error stack trace.
!image-2024-06-13-13-48-37-162.png|width=846,height=555!
was:
While running TPC-DS 10TB benchmark on the latest master branch locally, I've
encountered a failure in certain queries, specifically query 75, resulting in
the error "The read buffer is null in credit-based input channel".
Using a binary search approach, I identified the offending commit as
FLINK-33668. After reverting FLINK-33668 and subsequent commits, the issue
disappears. Re-applying FLINK-33668 to the branch re-introduces the error.
Please see the attached image for the error stack trace.
!image-2024-06-13-13-48-37-162.png!
> Job fails with "The read buffer is null in credit-based input channel" on
> TPC-DS 10TB benchmark
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-35587
> URL: https://issues.apache.org/jira/browse/FLINK-35587
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
> Affects Versions: 1.20.0
> Reporter: Junrui Li
> Priority: Major
> Attachments: image-2024-06-13-13-48-37-162.png
>
>
> While running TPC-DS 10TB benchmark on the latest master branch locally, I've
> encountered a failure in certain queries, specifically query 75, resulting in
> the error "The read buffer is null in credit-based input channel".
> Using a binary search approach, I identified the offending commit as
> FLINK-33668. After reverting FLINK-33668 and subsequent commits, the issue
> disappears. Re-applying FLINK-33668 to the branch re-introduces the error.
> Please see the attached image for the error stack trace.
> !image-2024-06-13-13-48-37-162.png|width=846,height=555!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
