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

Colocation groups config #667

Closed
wants to merge 1 commit into from
Closed

Conversation

rgrandl
Copy link
Contributor

@rgrandl rgrandl commented Oct 21, 2023

Right now we specify the components that should run together in a colocation group. For all the others we run them in their own groups. However, given that the group is the unit of deployment, we'll have to add configuration knobs that make sense per colocation group.

This PR provides some options to set per colocation group knobs in the config.

@rgrandl rgrandl force-pushed the colocation_options_discussion branch 3 times, most recently from 4e10205 to 9f913d1 Compare October 21, 2023 00:26
Right now we specify the components that should run together in a
colocation group. For all the others we run them in their own groups.
However, given that the group is the unit of deployment, we'll have to
add configuration knobs that make sense per colocation group.

This PR provides some options to set per colocation group knobs in the
config.
@rgrandl rgrandl force-pushed the colocation_options_discussion branch from 9f913d1 to 17a44b6 Compare October 21, 2023 00:30
@rgrandl
Copy link
Contributor Author

rgrandl commented Nov 5, 2024

We never reached a conclusion on what is the right way to specify collocation groups. The way we let users specify collocation groups as of now seems fine.

@rgrandl rgrandl closed this Nov 5, 2024
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.

1 participant