Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Let Pravega internal thread pool to deal with checkpoint #717

Closed
crazyzhou opened this issue Jul 13, 2023 · 0 comments · Fixed by #718
Closed

Let Pravega internal thread pool to deal with checkpoint #717

crazyzhou opened this issue Jul 13, 2023 · 0 comments · Fixed by #718
Assignees
@crazyzhou
Labels
area/reader kind/enhancement version/0.13.0

Comments

@crazyzhou
Copy link
Contributor

Problem description
Pravega has introduced a different way to initiate a checkpoint by using its internal thread pool in pravega/pravega#4816

As the thread pool in Pravega has more control, it's better to switch to use that.

Problem location
ReaderCheckpointHook

Suggestions for an improvement
@crazyzhou crazyzhou self-assigned this Jul 13, 2023
@crazyzhou crazyzhou changed the title Allow Pravega internal thread pool to deal with checkpoint Let Pravega internal thread pool to deal with checkpoint Jul 13, 2023
@crazyzhou crazyzhou mentioned this issue Jul 13, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crazyzhou crazyzhou

Labels
area/reader kind/enhancement version/0.13.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[issue-717] Let Pravega internal thread pool deal with checkpoint crazyzhou/flink-connectors
1 participant
@crazyzhou