-
Notifications
You must be signed in to change notification settings - Fork 466
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
[Doc] Server-side rejection of search requests based on resource #795
Comments
@JeffH-AWS - Hi Jeff, do you mind taking this one? It involves measuring shard resource consumption when running search related tasks. Thanks. |
Sure - is there a specific ask/scope defined somewhere? I'm not really sure what is being requested specifically after glancing at the other issues. Seems like it could be super broad. |
@JeffH-AWS: Scope and ask still TBD. There's active development going on for Task Consumer Integration, however, we'll have to wait till the PR is merged in to start documenting it. |
I'm going to split this into two issues and work them separately. One item is search back pressure, the other is task consumer integration. |
Sounds good! Feel free to close this as duplicate. |
I'm switching the label from 2.2 to 2.3, as discussed in the project roadmap meeting. |
Will start looking at this shortly as we're not in the run-up to the 2.3 release. |
It looks like milestone 2 is supposed to be included in 2.3:
|
Still trying to get a hold of @rramachand21 for details about milestone 2 from the meta/epic issue. |
I still have not received any information from the devs and there hasn't been a response on the feature issue. |
RFC- opensearch-project/OpenSearch#1329
Tracking issue- opensearch-project/OpenSearch#1181
POC's: Prabhu Senthamarai, Suresh N S, Ketan Verma, Pritkumar Ladani
The text was updated successfully, but these errors were encountered: