Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/opensearch-project/asynchronous-search
:arrow_forward: Run queries in the background and retrieve partial results along the way
https://github.com/opensearch-project/asynchronous-search
async asynchronous java long longrunning partial poll search timeouts
Last synced: 2 months ago
JSON representation
:arrow_forward: Run queries in the background and retrieve partial results along the way
- Host: GitHub
- URL: https://github.com/opensearch-project/asynchronous-search
- Owner: opensearch-project
- License: apache-2.0
- Created: 2021-04-06T02:05:17.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2024-05-29T06:36:30.000Z (8 months ago)
- Last Synced: 2024-05-29T08:15:55.097Z (8 months ago)
- Topics: async, asynchronous, java, long, longrunning, partial, poll, search, timeouts
- Language: Java
- Homepage: https://opensearch.org/docs/latest/search-plugins/async/index/
- Size: 45.5 MB
- Stars: 26
- Watchers: 18
- Forks: 47
- Open Issues: 33
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
README
[![Test and Build Workflow](https://github.com/opensearch-project/asynchronous-search/workflows/Test%20and%20Build%20Workflow/badge.svg)](https://github.com/opensearch-project/asynchronous-search/actions)
[![codecov](https://codecov.io/gh/opensearch-project/asynchronous-search/branch/main/graph/badge.svg)](https://codecov.io/gh/opensearch-project/asynchronous-search)# Asynchronous search
Asynchronous search makes it possible for users to run such queries without worrying about the query timing out.
These queries run in the background, and users can track the progress, and retrieve partial results as they become available.The asynchronous search plugin supports the below operations
**1. Submit asynchronous search**
```
POST /_plugins/_asynchronous_search?wait_for_completion_timeout=500ms&keep_on_completion=true&keep_alive=3d
{ "aggs": {
"city": {
"terms": {
"field": "city", "size": 50
}
}
}
}```
**2. Retrieve asynchronous search results**
```
GET /_plugins/_asynchronous_search/FjdITFhYbC1zVFdHVVV1MUd3UkxkMFEFMjQ1MzYUWHRrZjhuWUJXdFhxMmlCSW5HTE8BMQ==?keep_alive=3d
```**3. Delete an asynchronous search**
```
DELETE /_plugins/_asynchronous_search/FjdITFhYbC1zVFdHVVV1MUd3UkxkMFEFMjQ1MzYUWHRrZjhuWUJXdFhxMmlCSW5HTE8BMQ==
```**4. Stats for asynchronous search**
```
GET /_plugins/_asynchronous_search/stats
```**Tunable Settings**
1. `plugins.asynchronous_search.max_search_running_time` : Maximum running time for the search beyond which the search would be terminated
2. `plugins.asynchronous_search.node_concurrent_running_searches` : Concurrent searches running per coordinator node
3. `plugins.asynchronous_search.max_keep_alive` : Maximum keep alive for search which dictates how long the search is allowed to be present in the cluster
4. `plugins.asynchronous_search.max_wait_for_completion_timeout` : Maximum keep on completion to block for the search response
5. `plugins.asynchronous_search.persist_search_failures` : Persist asynchronous search result ending with search failure in system index## Setup
1. Check out this package from version control.
2. Launch Intellij IDEA, choose **Import Project**, and select the `settings.gradle` file in the root of this package.
3. To build from the command line, set `JAVA_HOME` to point to a JDK >= 8 before running `./gradlew`.
- Unix System
1. `export JAVA_HOME=jdk-install-dir`: Replace `jdk-install-dir` with the JAVA_HOME directory of your system.
2. `export PATH=$JAVA_HOME/bin:$PATH`
- Windows System
1. Find **My Computers** from file directory, right click and select **properties**.
2. Select the **Advanced** tab, select **Environment variables**.
3. Edit **JAVA_HOME** to path of where JDK software is installed.## Build
The project in this package uses the [Gradle](https://docs.gradle.org/current/userguide/userguide.html) build system. Gradle comes with excellent documentation that should be your first stop when trying to figure out how to operate or modify the build.
### Building from the command line
- `./gradlew build` builds and tests project.
- `./gradlew run` launches a single node cluster with the asynchronous search plugin installed.
- `./gradlew run -PnumNodes=3` launches a multi-node cluster with the asynchronous search plugin installed.### Integration tests
- `./gradlew integTest` launches a single node cluster with the asynchronous search plugin installed and runs all integ tests.
- `./gradlew integTest -PnumNodes=3` launches a multi-node cluster with the asynchronous search plugin installed and runs all integ tests.
- `./gradlew integTest -Dtests.class=*AsynchronousSearchRestIT` runs a single integ class
- `./gradlew integTest -Dtests.class=*AsynchronousSearchRestIT -Dtests.method="testSubmitWithRetainedResponse"` runs a single integ test method (remember to quote the test method name if it contains spaces)
- `./gradlew integTestRemote -Dtests.rest.cluster=localhost:9200 -Dtests.cluster=localhost:9200 -Dtests.clustername="docker-cluster" -Dhttps=true -Duser=admin -Dpassword=admin` launches integration tests against a local cluster and run tests with security`./gradlew integTestRemote -Dtests.rest.cluster=localhost:9200 -Dtests.cluster=localhost:9200 -Dtests.clustername="docker-cluster" -Dhttps=true -Duser=admin -Dpassword=` launches integration tests against a local cluster and run tests with security### Backwards compatibility tests
Note that while all backwards compatibility tests support the `-PcustomDistributionDownloadType=bundle` flag for testing with on the distribution bundle level, **only** changes previously published to the bundled distribution will be captured by these tests.
- `./gradlew asynSearchCluster#mixedClusterTask -Dtests.security.manager=false` launches a cluster of three nodes of bwc version of OpenSearch with async search plugin and tests backwards compatibility by performing rolling upgrade of one node with the current version of OpenSearch with async search plugin.
- `./gradlew asynSearchCluster#rollingUpgradeClusterTask -Dtests.security.manager=false` launches a cluster with three nodes of bwc version of OpenSearch with async search plugin and tests backwards compatibility by performing rolling upgrade of all nodes with the current version of OpenSearch with async search plugin.
- `./gradlew asynSearchCluster#fullRestartClusterTask -Dtests.security.manager=false` launches a cluster with three nodes of bwc version of OpenSearch with async search plugin and tests backwards compatibility by performing a full restart on the cluster upgrading all the nodes with the current version of OpenSearch with async search plugin.
- `./gradlew bwcTestSuite -Dtests.security.manager=false` runs all the above bwc tests combined.When launching a cluster using one of the above commands, logs are placed in `build/testclusters//logs`. Though the logs are tied to the console, in practices it's best to check the actual log file.
### Debugging
Sometimes it is useful to attach a debugger to either the OpenSearch cluster or the integ tests to see what's going on. When running unit tests, hit **Debug** from the IDE's gutter to debug the tests. For the OpenSearch cluster or the integ tests, first, make sure start a debugger listening on port `5005`.
To debug the server code, run:
```
./gradlew :integTest -Dcluster.debug # to start a cluster with debugger and run integ tests
```OR
```
./gradlew run --debug-jvm # to just start a cluster that can be debugged
```The OpenSearch server JVM will connect to a debugger attached to `localhost:5005`.
The IDE needs to listen for the remote JVM. If using Intellij you must set your debug configuration to "Listen to remote JVM" and make sure "Auto Restart" is checked.
You must start your debugger to listen for remote JVM before running the commands.To debug code running in an integration test (which exercises the server from a separate JVM), first, setup a remote debugger listening on port `8000`, and then run:
```
./gradlew :integTest -Dtest.debug
```The test runner JVM will connect to a debugger attached to `localhost:8000` before running the tests.
Additionally, it is possible to attach one debugger to the cluster JVM and another debugger to the test runner. First, make sure one debugger is listening on port `5005` and the other is listening on port `8000`. Then, run:
```
./gradlew :integTest -Dtest.debug -Dcluster.debug
```## Getting Help
If you find a bug, or have a feature request, please don't hesitate to open an issue in this repository.
For more information, see the [project website](https://opensearch.org/) and [technical documentation](https://opensearch.org/docs/latest/search-plugins/async/index/). If you need help and are unsure where to open an issue, try the OpenSearch [Forum](https://forum.opensearch.org/).
## Security
See [CONTRIBUTING](CONTRIBUTING.md#security-issue-notifications) for more information.
## License
This project is licensed under the [Apache v2.0 License](LICENSE).
## Copyright
Copyright OpenSearch Contributors. See [NOTICE](NOTICE) for details.