2019-06-13 05:18:55 -04:00
|
|
|
import org.elasticsearch.gradle.test.RestIntegTestTask
|
|
|
|
|
|
|
|
|
|
apply plugin: 'elasticsearch.testclusters'
|
2018-10-18 15:33:33 -04:00
|
|
|
apply plugin: 'elasticsearch.standalone-rest-test'
|
|
|
|
|
apply plugin: 'elasticsearch.rest-test'
|
|
|
|
|
|
|
|
|
|
dependencies {
|
2019-11-14 06:01:23 -05:00
|
|
|
testCompile project(path: xpackProject('plugin').path, configuration: 'testArtifacts')
|
2018-10-18 15:33:33 -04:00
|
|
|
}
|
|
|
|
|
|
2019-06-13 05:18:55 -04:00
|
|
|
File repoDir = file("$buildDir/testclusters/repo")
|
|
|
|
|
|
|
|
|
|
integTest.runner {
|
2019-11-14 06:01:23 -05:00
|
|
|
/* To support taking index snapshots, we have to set path.repo setting */
|
|
|
|
|
systemProperty 'tests.path.repo', repoDir
|
2019-01-23 11:46:31 -05:00
|
|
|
}
|
|
|
|
|
|
2019-06-13 05:18:55 -04:00
|
|
|
testClusters.integTest {
|
2019-11-14 06:01:23 -05:00
|
|
|
testDistribution = 'DEFAULT'
|
|
|
|
|
numberOfNodes = 4
|
|
|
|
|
|
|
|
|
|
setting 'path.repo', repoDir.absolutePath
|
|
|
|
|
setting 'xpack.ilm.enabled', 'true'
|
|
|
|
|
setting 'xpack.security.enabled', 'false'
|
|
|
|
|
setting 'xpack.watcher.enabled', 'false'
|
|
|
|
|
setting 'xpack.monitoring.enabled', 'false'
|
|
|
|
|
setting 'xpack.ml.enabled', 'false'
|
|
|
|
|
setting 'xpack.license.self_generated.type', 'trial'
|
|
|
|
|
setting 'indices.lifecycle.poll_interval', '1000ms'
|
[7.x] Add ILM histore store index (#50287) (#50345)
* Add ILM histore store index (#50287)
* Add ILM histore store index
This commit adds an ILM history store that tracks the lifecycle
execution state as an index progresses through its ILM policy. ILM
history documents store output similar to what the ILM explain API
returns.
An example document with ALL fields (not all documents will have all
fields) would look like:
```json
{
"@timestamp": 1203012389,
"policy": "my-ilm-policy",
"index": "index-2019.1.1-000023",
"index_age":123120,
"success": true,
"state": {
"phase": "warm",
"action": "allocate",
"step": "ERROR",
"failed_step": "update-settings",
"is_auto-retryable_error": true,
"creation_date": 12389012039,
"phase_time": 12908389120,
"action_time": 1283901209,
"step_time": 123904107140,
"phase_definition": "{\"policy\":\"ilm-history-ilm-policy\",\"phase_definition\":{\"min_age\":\"0ms\",\"actions\":{\"rollover\":{\"max_size\":\"50gb\",\"max_age\":\"30d\"}}},\"version\":1,\"modified_date_in_millis\":1576517253463}",
"step_info": "{... etc step info here as json ...}"
},
"error_details": "java.lang.RuntimeException: etc\n\tcaused by:etc etc etc full stacktrace"
}
```
These documents go into the `ilm-history-1-00000N` index to provide an
audit trail of the operations ILM has performed.
This history storage is enabled by default but can be disabled by setting
`index.lifecycle.history_index_enabled` to `false.`
Resolves #49180
* Make ILMHistoryStore.putAsync truly async (#50403)
This moves the `putAsync` method in `ILMHistoryStore` never to block.
Previously due to the way that the `BulkProcessor` works, it was possible
for `BulkProcessor#add` to block executing a bulk request. This was bad
as we may be adding things to the history store in cluster state update
threads.
This also moves the index creation to be done prior to the bulk request
execution, rather than being checked every time an operation was added
to the queue. This lessens the chance of the index being created, then
deleted (by some external force), and then recreated via a bulk indexing
request.
Resolves #50353
2019-12-20 14:33:36 -05:00
|
|
|
setting 'logger.org.elasticsearch.xpack.core.ilm', 'TRACE'
|
|
|
|
|
setting 'logger.org.elasticsearch.xpack.ilm', 'TRACE'
|
2018-10-18 15:33:33 -04:00
|
|
|
}
|
