Managing multiple clusters recipe #429
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Westwooo
force-pushed
the
managing_multiple_clusters
branch
4 times, most recently
from
bce2cb7
to
fd34ad2
Compare
ingenthr
approved these changes
Sep 5, 2024
Comment on lines
11
to
16
| ├───┼────────┼───────┼────────────────────────┼───────────────┼──────────────────────┼─────────────────┤ | ||
| │ 0 │ false │ true │ meekjoycekreynolds │ Administrator │ my-org │ CBShell Testing │ | ||
| │ 1 │ false │ false │ local │ Administrator │ │ │ | ||
| │ 2 │ false │ true │ bronzegeraldjaysussman │ Administrator │ my-org │ CBShell Testing │ | ||
| │ 3 │ true │ true │ obligingfaronmoller │ Administrator │ my-org │ CBShell Testing │ | ||
| ╰───┴────────┴───────┴────────────────────────┴───────────────┴──────────────────────┴─────────────────╯ |
There was a problem hiding this comment.
Minor improvement if you want, give them identifiers that match a narrative. like "localdev" and "systemtest" and "prod" and "ci".
Comment on lines
89
to
90
| While it is somewhat useful to know the free memory that each cluster has, it'd be more useful for our healthcheck to know the memory utilization for each cluster. | ||
| Unfortunately the info returned by `nodes` does not include the memory utilization, however there are two columns that can be used to calculate this: `memory_free` and `memory_total`. |
There was a problem hiding this comment.
Again, quite cool, but it might be neat to fit it into a narrative. LIke it's useful to find a test cluster with space to create a bucket, yadda, yadda.
There was a problem hiding this comment.
There are kind of two narratives, first performing health checks, then using this data to allocate a bucket. I've changed this to make it more linked to the health check narrative and have the bucket spiel later on:
Now that we understand the resources being used by our cluster we can use this information to aide us when deploying a new bucket.
Imagine that we want to create a 1GB bucket on any one of our clusters.
fd34ad2
to
e856a48
Compare
Fix links in similarity search recipe
Westwooo
force-pushed
the
managing_multiple_clusters
branch
from
e856a48
to
eb32e48
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.