This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #887 from davidwadden/es5-rest-client
Elasticsearch 5 REST Client
- Loading branch information
Showing
24 changed files
with
2,461 additions
and
325 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,67 @@ | ||
# ES5 Persistence | ||
|
||
This module provides ES5 persistence when indexing workflows and tasks. | ||
|
||
## Usage | ||
|
||
This module uses the following configuration options: | ||
|
||
* `workflow.elasticsearch.instanceType` - This determines the type of ES instance we are using with conductor. | ||
The two values are either `MEMORY` or `EXTERNAL`. | ||
If `MEMORY`, then an embedded server will be run. | ||
Default is `MEMORY`. | ||
* `workflow.elasticsearch.url` - A comma separated list of schema/host/port of the ES nodes to communicate with. | ||
Schema can be ignored when using `tcp` transport; otherwise, you must specify `http` or `https`. | ||
If using the `http` or `https`, then conductor will use the REST transport protocol. | ||
* `workflow.elasticsearch.index.name` - The name of the workflow and task index. | ||
Defaults to `conductor` | ||
* `workflow.elasticsearch.tasklog.index.name` - The name of the task log index. | ||
Defaults to `task_log` | ||
|
||
### Embedded Configuration | ||
|
||
If `workflow.elasticsearch.instanceType=MEMORY`, then you can configure the embedded server using the following configurations: | ||
|
||
* `workflow.elasticsearch.embedded.port` - The starting port of the embedded server. | ||
This is the port used for the TCP transport. | ||
It will also use this + 100 in order to setup the http transport. | ||
Default is `9200` | ||
* `workflow.elasticsearch.embedded.cluster.name` - The name of the embedded cluster name. | ||
Default is `elasticsearch_test` | ||
* `workflow.elasticsearch.embedded.host` - The host of the embedded server. | ||
Default is `127.0.0.1` | ||
|
||
### REST Transport | ||
|
||
If you are using AWS ElasticSearch, you should use the `rest` transport as that's the only version transport that they support. | ||
However, this module currently only works with open IAM, VPC version of ElasticSearch. | ||
Eventually, we should create ES modules that can be loaded in to support authentication and request signing, but this currently does not support that. | ||
|
||
### Example Configurations | ||
|
||
**In-memory ES with TCP transport** | ||
|
||
``` | ||
workflow.elasticsearch.instanceType=MEMORY | ||
``` | ||
|
||
**In-memory ES with REST transport** | ||
|
||
``` | ||
workflow.elasticsearch.instanceType=MEMORY | ||
workflow.elasticsearch.url=http://localhost:9300 | ||
``` | ||
|
||
**ES with TCP transport** | ||
|
||
``` | ||
workflow.elasticsearch.instanceType=EXTERNAL | ||
workflow.elasticsearch.url=127.0.0.1:9300 | ||
``` | ||
|
||
**ES with REST transport** | ||
|
||
``` | ||
workflow.elasticsearch.instanceType=EXTERNAL | ||
workflow.elasticsearch.url=http://127.0.0.1:9200 | ||
``` |
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
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
Oops, something went wrong.