mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
Isolate esvm clusters by purpose
Attempting to run multiple elasticsearch clusters on the same host without specifying different cluster names actually triggers the discovery behaviors of elasticsearch, which adds the second es process as another node of the original cluster. This means that despite running on different ports, our test setups of elasticsearch actually attempt to modify the main dev setup.
This commit is contained in:
parent
ec978ea0d4
commit
255d9a2f28
1 changed files with 9 additions and 0 deletions
|
@ -28,6 +28,9 @@ module.exports = function (grunt) {
|
|||
config: {
|
||||
path: {
|
||||
data: dataDir
|
||||
},
|
||||
cluster: {
|
||||
name: 'esvm-dev'
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -39,6 +42,9 @@ module.exports = function (grunt) {
|
|||
config: {
|
||||
http: {
|
||||
port: 9210
|
||||
},
|
||||
cluster: {
|
||||
name: 'esvm-test'
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -50,6 +56,9 @@ module.exports = function (grunt) {
|
|||
config: {
|
||||
http: {
|
||||
port: uiConfig.servers.elasticsearch.port
|
||||
},
|
||||
cluster: {
|
||||
name: 'esvm-ui'
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue