Add a track for Metricbeat data #56
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,179 @@ | ||
| { | ||
| "name": "append-no-conflicts", | ||
| "description": "Indexes the whole document corpus using Elasticsearch default settings. We only adjust the number of replicas as we benchmark a single node cluster and Rally will only start the benchmark if the cluster turns green. Document ids are unique so all index operations are append only. After that a couple of queries are run.", | ||
| "default": true, | ||
| "schedule": [ | ||
| { | ||
| "operation": "delete-index" | ||
| }, | ||
| { | ||
| "operation": { | ||
| "operation-type": "create-index", | ||
| "settings": {{index_settings | default({}) | tojson}} | ||
| } | ||
| }, | ||
| { | ||
| "name": "check-cluster-health", | ||
| "operation": { | ||
| "operation-type": "cluster-health", | ||
| "index": "metricbeat", | ||
| "request-params": { | ||
| "wait_for_status": "{{cluster_health | default('green')}}", | ||
| "wait_for_no_relocating_shards": "true" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "operation": "index-append", | ||
| "warmup-time-period": 0, | ||
| "clients": {{bulk_indexing_clients | default(8)}} | ||
| }, | ||
| { | ||
| "name": "refresh-after-index", | ||
| "operation": "refresh", | ||
| "clients": 1 | ||
| }, | ||
| { | ||
| "operation": "force-merge", | ||
| "clients": 1 | ||
| }, | ||
| { | ||
| "name": "refresh-after-force-merge", | ||
| "operation": "refresh", | ||
| "clients": 1 | ||
| }, | ||
| { | ||
| "operation": "index-stats", | ||
|
There was a problem hiding this comment. I don't think we need to benchmark index stats here? |
||
| "clients": 1, | ||
| "warmup-iterations": 0, | ||
| "iterations": 1000, | ||
| "target-throughput": 100 | ||
| }, | ||
| { | ||
| "operation": "node-stats", | ||
|
There was a problem hiding this comment. I don't think we need to benchmark node stats here? |
||
| "clients": 1, | ||
| "warmup-iterations": 0, | ||
| "iterations": 1000, | ||
| "target-throughput": 100 | ||
| }, | ||
| { | ||
| "operation": "default", | ||
|
There was a problem hiding this comment. Is it intentional that the aggregation queries are not referenced here? |
||
| "clients": 1, | ||
| "warmup-iterations": 0, | ||
| "iterations": 1000, | ||
| "target-throughput": 50 | ||
| } | ||
| ] | ||
| }, | ||
| { | ||
| "name": "append-no-conflicts-index-only", | ||
|
There was a problem hiding this comment. I would not include any of the other challenges unless you are interested in those metrics. |
||
| "description": "Indexes the whole document corpus using Elasticsearch default settings. We only adjust the number of replicas as we benchmark a single node cluster and Rally will only start the benchmark if the cluster turns green. Document ids are unique so all index operations are append only.", | ||
| "schedule": [ | ||
| { | ||
| "operation": "delete-index" | ||
| }, | ||
| { | ||
| "operation": { | ||
| "operation-type": "create-index", | ||
| "settings": {{index_settings | default({}) | tojson}} | ||
| } | ||
| }, | ||
| { | ||
| "name": "check-cluster-health", | ||
| "operation": { | ||
| "operation-type": "cluster-health", | ||
| "index": "metricbeat", | ||
| "request-params": { | ||
| "wait_for_status": "{{cluster_health | default('green')}}", | ||
| "wait_for_no_relocating_shards": "true" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "operation": "index-append", | ||
| "warmup-time-period": 0, | ||
| "clients": {{bulk_indexing_clients | default(8)}} | ||
| }, | ||
| { | ||
| "operation": "force-merge", | ||
| "clients": 1 | ||
| } | ||
| ] | ||
| }, | ||
| { | ||
| "name": "append-sorted-no-conflicts", | ||
| "description": "Indexes the whole document corpus in an index sorted by country_code field in ascending order. Document ids are unique so all index operations are append only.", | ||
| "schedule": [ | ||
| { | ||
| "operation": "delete-index" | ||
| }, | ||
| { | ||
| "operation": { | ||
| "operation-type": "create-index", | ||
| "settings": { | ||
| "index.sort.field": ["country_code.raw", "admin1_code.raw"], | ||
| "index.sort.order": ["asc", "asc"] | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "name": "check-cluster-health", | ||
| "operation": { | ||
| "operation-type": "cluster-health", | ||
| "index": "metricbeat", | ||
| "request-params": { | ||
| "wait_for_status": "{{cluster_health | default('green')}}", | ||
| "wait_for_no_relocating_shards": "true" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "operation": "index-append", | ||
| "warmup-time-period": 0, | ||
| "clients": {{bulk_indexing_clients | default(8)}} | ||
| }, | ||
| { | ||
| "operation": "force-merge", | ||
| "clients": 1 | ||
| } | ||
| ] | ||
| }, | ||
| { | ||
| "name": "append-fast-with-conflicts", | ||
| "description": "Indexes the whole document corpus using a setup that will lead to a larger indexing throughput than the default settings. Rally will produce duplicate ids in 25% of all documents (not configurable) so we can simulate a scenario with appends most of the time and some updates in between.", | ||
| "schedule": [ | ||
| { | ||
| "operation": "delete-index" | ||
| }, | ||
| { | ||
| "operation": { | ||
| "operation-type": "create-index", | ||
| "settings": { | ||
| "index.refresh_interval": "30s", | ||
| "index.number_of_shards": 6, | ||
| "index.translog.flush_threshold_size": "4g" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "name": "check-cluster-health", | ||
| "operation": { | ||
| "operation-type": "cluster-health", | ||
| "index": "metricbeat", | ||
| "request-params": { | ||
| "wait_for_status": "{{cluster_health | default('green')}}", | ||
| "wait_for_no_relocating_shards": "true" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "operation": "index-update", | ||
| "warmup-time-period": 0, | ||
| "clients": {{bulk_indexing_clients | default(8)}} | ||
| }, | ||
| { | ||
| "operation": "force-merge", | ||
| "clients": 1 | ||
| } | ||
| ] | ||
| } | ||
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 |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| documents.json | ||
|
There was a problem hiding this comment. This file is needed for the script that prepares the corpus for offline usage (see https://github.com/elastic/rally-tracks/blob/master/download.sh). I think when you're done this should only contain the compressed corpus file (+ a smaller file that contains the test corpus, see our docs). There was a problem hiding this comment. I think this should contain: For details please see my comment above. |
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess bulk-indexing the document corpus is considered more of a setup task here (i.e. you're not interested in bulk-indexing throughput)? In that case setting the warmup time-period to zero is fine.