Configure dhstore key sharding #1759
Closed
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
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #1759 +/- ##
==========================================
+ Coverage 51.25% 51.30% +0.04%
==========================================
Files 101 101
Lines 11253 11263 +10
==========================================
+ Hits 5768 5778 +10
- Misses 4901 4903 +2
+ Partials 584 582 -2
☔ View full report in Codecov by Sentry. |
masih
added a commit
that referenced
this pull request
May 18, 2023
Make a deployable container from `dh-key-sharding` branch for testing the sharding mechanims in dev. See: #1759
masih
added a commit
that referenced
this pull request
May 18, 2023
Make a deployable container from `dh-key-sharding` branch for testing the sharding mechanims in dev. See: #1759
masih
added a commit
that referenced
this pull request
May 18, 2023
Deploy a new node called `dana` in `dev` wht the head of #1759 to test out sharding mechanism across dhstore cluster. The indexer node is configured to read ads from the S3 bucket populated by `ago`.
masih
added a commit
that referenced
this pull request
May 18, 2023
Deploy a new node called `dana` in `dev` wht the head of #1759 to test out sharding mechanism across dhstore cluster. The indexer node is configured to read ads from the S3 bucket populated by `ago`.
Deploy a new node called `dana` in `dev` wht the head of #1759 to test out sharding mechanism across dhstore cluster. The indexer node is configured to read ads from the S3 bucket populated by `ago`.
Node group is used by indexer nodes and had ha max of 3
* Change ExtendedProviders behaviour to 'replace' instead of 'add' Removed ExtendedProviders additive behaviour. Each ExtendedProviders advertisement will have to have a full set of ExtendedProviders from now on (no deltas). Additive behaviour makes updates and removals harder and is generally counterintuitive.
* Bump up dhstore CPU cores to 7 * Reduce ago ingest worker count to 5 * Temporarily disable ago writes to let dhstore do compaction
|
Something got messed up in the last commit. Replacing this PR with #1778 |
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.
Enables DH key sharding in core.