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

DNM: cc wip for testing #30446

Closed
wants to merge 6 commits into from
Closed

DNM: cc wip for testing #30446

wants to merge 6 commits into from

Conversation

def-
Copy link
Contributor

@def- def- commented Nov 12, 2024

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

benesch and others added 4 commits November 12, 2024 00:36
Rather than inferring the "cc"-ness of a cluster from its name. This will
be important for self hosted Materialize, where customers will be able
to install their own cluster size names. "cc"-ness defaults to true if not
explicitly disabled, since "cc" clusters get modern behavior that we want
all self-hosted clustrs to get.

Also, make it possible to disable using disk for a given size by setting
the disk limit to 0, even for sizes marked as "cc", to support users
that will be running Materialize on nodes without local disks.
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.

2 participants