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

Shard Indexing Pressure changes to be merged #1336

Merged
merged 11 commits into from
Oct 7, 2021

Conversation

getsaurabh02
Copy link
Member

@getsaurabh02 getsaurabh02 commented Oct 6, 2021

Description

This PR aims to merge the changes for the shard level indexing back-pressure changes from the feature branch. The changes were divided into small manageable chunks as part of the following PRs against the feature branch.

Issues Resolved

#478

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

getsaurabh02 and others added 11 commits October 6, 2021 20:51
…h-project#838)

* Add Shard Indexing Pressure Store (opensearch-project#478)

Signed-off-by: Saurabh Singh <sisurab@amazon.com>

* Added comments and shard allocation based on compute in hot store.

Signed-off-by: Saurabh Singh <sisurab@amazon.com>

Co-authored-by: Saurabh Singh <sisurab@amazon.com>
…pensearch-project#945)

It introduces a Memory Manager for Shard Indexing Pressure. It is responsible for increasing and decreasing the allocated shard limit based on incoming requests, and validate the current values against the thresholds.

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
…arch-project#1015)

* Add ShardIndexingPressure framework level construct and related Stats artefacts.
* Test and code refactoring for shard indexing pressure.
* Moved the average calculation logic to common memory manager util.
* Add wrapper for releasable in ShardIndexingPressure operations.

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
… pressure interfaces. (opensearch-project#1084)

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
…rch-project#1171)

* Add shard indexing pressure metric/stats via rest end point.

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
Signed-off-by: Saurabh Singh <sisurab@amazon.com>
Signed-off-by: Rabi Panda <adnapibar@gmail.com>
@getsaurabh02 getsaurabh02 changed the title Indexing pressure pr Shard Indexing Pressure changes to be merged Oct 6, 2021
@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 67b0be6

@opensearch-ci-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 67b0be6

@adnapibar
Copy link
Contributor

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 67b0be6

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Check success 67b0be6
Log 605

Reports 605

@adnapibar adnapibar added the v1.2.0 Issues related to version 1.2.0 label Oct 6, 2021
Copy link
Contributor

@adnapibar adnapibar left a comment

Choose a reason for hiding this comment

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

👍

@adnapibar adnapibar merged commit 3665daf into opensearch-project:main Oct 7, 2021
getsaurabh02 added a commit to getsaurabh02/OpenSearch that referenced this pull request Oct 7, 2021
Shard level indexing pressure improves the current Indexing Pressure framework which performs memory accounting at node level and rejects the requests. This takes a step further to have rejections based on the memory accounting at shard level along with other key performance factors like throughput and last successful requests.

**Key features**
- Granular tracking of indexing tasks performance, at every shard level, for each node role i.e. coordinator, primary and replica.
- Smarter rejections by discarding the requests intended only for problematic index or shard, while still allowing others to continue (fairness in rejection).
- Rejections thresholds governed by combination of configurable parameters (such as memory limits on node) and dynamic parameters (such as latency increase, throughput degradation).
- Node level and shard level indexing pressure statistics exposed through stats api.
- Integration of Indexing pressure stats with Plugins for for metric visibility and auto-tuning in future.
- Control knobs to tune to the key performance thresholds which control rejections, to address any specific requirement or issues.
- Control knobs to run the feature in shadow-mode or enforced-mode. In shadow-mode only internal rejection breakdown metrics will be published while no actual rejections will be performed.

The changes were divided into small manageable chunks as part of the following PRs against a feature branch.

- Add Shard Indexing Pressure Settings. opensearch-project#716
- Add Shard Indexing Pressure Tracker. opensearch-project#717
- Refactor IndexingPressure to allow extension. opensearch-project#718
- Add Shard Indexing Pressure Store opensearch-project#838
- Add Shard Indexing Pressure Memory Manager opensearch-project#945
- Add ShardIndexingPressure framework level construct and Stats opensearch-project#1015
- Add Indexing Pressure Service which acts as orchestrator for IP opensearch-project#1084
- Add plumbing logic for IndexingPressureService in Transport Actions. opensearch-project#1113
- Add shard indexing pressure metric/stats via rest end point. opensearch-project#1171
- Add shard indexing pressure integration tests. opensearch-project#1198

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
Co-authored-by: Saurabh Singh <sisurab@amazon.com>
Co-authored-by: Rabi Panda <adnapibar@gmail.com>

private final Map<ShardId, ShardIndexingPressureTracker> shardIndexingPressureHotStore =
ConcurrentCollections.newConcurrentMapWithAggressiveConcurrency();
private final Map<ShardId, ShardIndexingPressureTracker> shardIndexingPressureColdStore = new HashMap<>();
Copy link
Collaborator

Choose a reason for hiding this comment

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

@adnapibar I believe shardIndexingPressureColdStore should be using safe concurrent structure or synchronization, much like shardIndexingPressureHotStore, thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

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

That was the initial proposal in the Store PR. However we later realised we don't need strong concurrency guarantees on cold store, since ordering/uniqueness of trackers is governed by Hot Store anyways. So we decided to change to it to a regular map.

Copy link
Collaborator

Choose a reason for hiding this comment

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

👍 thank you @getsaurabh02

tlfeng pushed a commit that referenced this pull request Oct 11, 2021
Shard level indexing pressure improves the current Indexing Pressure framework which performs memory accounting at node level and rejects the requests. This takes a step further to have rejections based on the memory accounting at shard level along with other key performance factors like throughput and last successful requests.

**Key features**
- Granular tracking of indexing tasks performance, at every shard level, for each node role i.e. coordinator, primary and replica.
- Smarter rejections by discarding the requests intended only for problematic index or shard, while still allowing others to continue (fairness in rejection).
- Rejections thresholds governed by combination of configurable parameters (such as memory limits on node) and dynamic parameters (such as latency increase, throughput degradation).
- Node level and shard level indexing pressure statistics exposed through stats api.
- Integration of Indexing pressure stats with Plugins for for metric visibility and auto-tuning in future.
- Control knobs to tune to the key performance thresholds which control rejections, to address any specific requirement or issues.
- Control knobs to run the feature in shadow-mode or enforced-mode. In shadow-mode only internal rejection breakdown metrics will be published while no actual rejections will be performed.

The changes were divided into small manageable chunks as part of the following PRs against a feature branch.

- Add Shard Indexing Pressure Settings. #716
- Add Shard Indexing Pressure Tracker. #717
- Refactor IndexingPressure to allow extension. #718
- Add Shard Indexing Pressure Store #838
- Add Shard Indexing Pressure Memory Manager #945
- Add ShardIndexingPressure framework level construct and Stats #1015
- Add Indexing Pressure Service which acts as orchestrator for IP #1084
- Add plumbing logic for IndexingPressureService in Transport Actions. #1113
- Add shard indexing pressure metric/stats via rest end point. #1171
- Add shard indexing pressure integration tests. #1198

Signed-off-by: Saurabh Singh <sisurab@amazon.com>
Co-authored-by: Saurabh Singh <sisurab@amazon.com>
Co-authored-by: Rabi Panda <adnapibar@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.2.0 Issues related to version 1.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants