Hi all! I have spinned up an Application Load Balancer and an autoscaling group on AWS and the Ignite discovery using TcpDiscoveryAlbIpFinder works as expected.
- On startup nodes discover each other. - On ec2 node down, connection is lost and the cluster decreases. - On an extra node addition the cluster size increases This contribution is essential since the Previous ELB based discovery uses the Classic Load Balancer which is still available however AWS advices users to use the Application one. [1] While my pull request gets reviewed I will also have a look at the IGNITE-12398 [2] issue which has to do with the S3 discovery. Another idea would also be to implement a `TCP Load Balancer based` discovery. In order to test this issue and future ones I implemented some terraform scripts (which I shall use for other issues too) [3]. If some automated e2e testing on AWS is being considered they might be of value. I can help on implementing those tests by provisioning the infrastructure in an automated way and validate the discovery. [1] https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-to-application-load-balancer.html [2] https://issues.apache.org/jira/browse/IGNITE-12398 [3] https://github.com/gkatzioura/ignite-aws-deploy Kind regards, *Emmanouil Gkatziouras* https://egkatzioura.com/ | https://www.linkedin.com/in/gkatziourasemmanouil/ https://github.com/gkatzioura On Tue, 14 Jan 2020 at 22:22, Denis Magda <dma...@apache.org> wrote: > Hi Emmanouil, > > Agree, let's check that the IP finder functions normally in the cloud > environment and the mock tests can be used for regular testing on Team > City. That's the way we tested other environment-specific IP finders > including the Kubernetes one. > > Let us know once the IP finder is tested on AWS and then we can proceed > with the review. > > - > Denis > > > On Tue, Jan 14, 2020 at 2:47 AM Emmanouil Gkatziouras < > gkatzio...@gmail.com> > wrote: > > > Hi all! > > > > With regards to the `Node Discovery Using AWS Application ELB` issue [1] > > I made this pull request to fix the merge conflicts [2]. > > Will also check if the concerns described on the mailing list topic > > `Volunteer needed: AWS Elastic Load Balancer IP Finders implemented` are > > addressed [3] > > Since I did not test it on an AWS infrastructure the next step would be > to > > spin up some AWS resources and test it. > > By doing so it will help me on checking the Amazon S3 Based Discovery > issue > > [4] . > > I will try to make the deployment as infrastructure as code, and see if > > this can be of value for the ignite project and testing. > > > > Kind regards, > > Emmanouil > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8617 > > [2] https://github.com/apache/ignite/pull/7247 > > [3] > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Volunteer-needed-AWS-Elastic-Load-Balancer-IP-Finders-implemented-td33847.html#a39793 > > [4] https://issues.apache.org/jira/browse/IGNITE-12398 > > > > > > > >
