Skip to content

Do not fail stage after already done#20002

Merged
losipiuk merged 1 commit intotrinodb:masterfrom
losipiuk:lo/ignore-stage-fail-after-finish
Dec 2, 2023
Merged

Do not fail stage after already done#20002
losipiuk merged 1 commit intotrinodb:masterfrom
losipiuk:lo/ignore-stage-fail-after-finish

Conversation

@losipiuk
Copy link
Member

@losipiuk losipiuk commented Dec 2, 2023

Ignore failure within stage execution if it already done. This is to work around the problem which was introduced with 39b04491c05. With that change we close EventDrivenTaskSource when stage completes, and as a result of that it may emit an failure event due to internall processes being cancelled.
Handling of event in StageExecution.fail() did close a number of objects needed for query completion (see createStageExecutionCloser()). As a result the query could hang.

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

Ignore failure within stage execution if it already done.
This is to work around the problem which was introduced with
trinodb@39b04491c05.
With that change we close EventDrivenTaskSource when stage completes,
and as a result of that it may emit an failure event due to internall
processes being cancelled.
Handling of event in `StageExecution.fail()` did close a number of
objects needed for query completion (see createStageExecutionCloser()).
As a result the query could hang.
@losipiuk losipiuk merged commit 3c498b7 into trinodb:master Dec 2, 2023
@github-actions github-actions bot added this to the 435 milestone Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants