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.

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

Removing one task per call layer on control plane. #5012

Merged
merged 2 commits into from
May 31, 2024

Conversation

fulmicoton
Copy link
Contributor

They are useless. The control plane is already an actor.

@fulmicoton fulmicoton requested a review from guilload May 21, 2024 06:16
They are useless. The control plane is already an actor.
@fulmicoton fulmicoton force-pushed the remove-non-sense-on-task-per-call branch from 913cc15 to d5a5659 Compare May 21, 2024 06:41
.stack_delete_source_layer(OneTaskPerCallLayer)
.stack_get_or_create_open_shards_layer(OneTaskPerCallLayer)
.stack_layer(CP_GRPC_SERVER_METRICS_LAYER.clone())
.stack_layer(LoadShedLayer::new(100))
Copy link
Member

Choose a reason for hiding this comment

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

Now that we have optimized a bunch of metastore queries, I wonder whether we should bump up that value. Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The load shedder? I think 100 is plenty for the control plane.

Copy link
Member

Choose a reason for hiding this comment

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

Maybe not at midnight UTC when 3000+ new shards need to be opened.

@fulmicoton fulmicoton merged commit ba47faa into main May 31, 2024
4 of 5 checks passed
@fulmicoton fulmicoton deleted the remove-non-sense-on-task-per-call branch May 31, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants