Hello team ,
I had been running Elastic cluster on traditional VM's with following architecture .
3 master Nodes
3 Client Nodes
5 Hot Data Nodes
and 3 Warm Data nodes ( Implemented Hot warm architecture from elastic blog )
( Each node has master nodes entry as unicast host lists , with 2 minimum number of masters set ,
#discovery.zen.ping.unicast.hosts: ["X.X.X.X:9300", "X.X.X.X:9300", "X.X.X.X:9300"]
#discovery.zen.minimum_master_nodes: 2
#discovery.zen.ping_timeout: 30s
This was running perfectly fine from last 2 years .
Now we are trying to move this complete architecture to aws and want to use aws ec2 discovery plugin of elasticsearch .
We have provisioned 3 instances and changed the discovery settings to
discovery.zen.hosts_provider: ec2 ( aws ec2 discovery plugin )
discovery.ec2.groups: staging-elasticsearch-cluster ( security group name )
discovery.ec2.tag.environment: staging ( tag with name environment and value staging )
This too is working fine for me .
Now scenario is I have to implement the earlier architecture ( 3 master , 3 Client , 5 Hot Nodes , 3 Warn Nodes) using ec2 discovery plugin ,
So the actual thing which I am trying to understand is how each master will be discovered using ec2 plugin . because we have now different node types deployed .
Do we have to make some extra settings to implement same .
Hoping for some real scenario replies .
Regards