Skip to content

do not call finalize after exception#50907

Merged
CheSema merged 10 commits intoClickHouse:masterfrom
CheSema:memory-leak
Jun 23, 2023
Merged

do not call finalize after exception#50907
CheSema merged 10 commits intoClickHouse:masterfrom
CheSema:memory-leak

Conversation

@CheSema
Copy link
Copy Markdown
Member

@CheSema CheSema commented Jun 12, 2023

StorageS3Sink handle exceptions in a wrong way.
test_upload_s3_fail_create_multi_part_upload -- showed that object is tried to be written at onException method after exception
test_upload_s3_fail_upload_part_when_multi_part_upload -- the same, but it ends up as a FATAL error

test_heavy_insert_select_check_memory -- just good test, let it be

Continuation for #50274
Blocked by #50395

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

@CheSema CheSema marked this pull request as ready for review June 12, 2023 21:51
@robot-clickhouse-ci-2 robot-clickhouse-ci-2 added the pr-not-for-changelog This PR should not be mentioned in the changelog label Jun 12, 2023
@robot-clickhouse-ci-2
Copy link
Copy Markdown
Contributor

robot-clickhouse-ci-2 commented Jun 12, 2023

This is an automated comment for commit 977cd03 with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🟡 pending

Check nameDescriptionStatus
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR🟡 pending
Mergeable CheckChecks if all other necessary checks are successful🟢 success

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I was scared reading this function name, because it is the same as C's abort. Maybe cancel?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

void onCancel() is already in use.
Actually it is better to fix onCancel as well. But I do not have a test for it. And it is not urgent at all if compare to the changes in onException.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be release is fine here.

@CheSema CheSema force-pushed the memory-leak branch 3 times, most recently from caa8e3d to c0671ca Compare June 13, 2023 05:30
@CheSema CheSema requested a review from Avogar June 22, 2023 09:20
@Avogar Avogar self-assigned this Jun 22, 2023
@CheSema
Copy link
Copy Markdown
Member Author

CheSema commented Jun 23, 2023

Stateless tests (release)
01193_metadata_loading -- #51185

Stateless Tests (msan)
00534_functions_bad_arguments12
00534_functions_bad_arguments4_long -- #50619

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants