Yes today in a demo Swapnil showed this issue to us. We need to investigate the load balancer extension and see the reason for this problem.
Thanks On Wed, Jul 22, 2015 at 9:21 AM, Swapnil Patil <swapnil.r...@gmail.com> wrote: > Hi Imesh, Lakmal, > > I observed the extension log to find out that, extension's configure > method is indeed called after member is activated but before it is added to > cluster. I assume that is why extension cannot see the newly activated > member as a part of cluster. > > I hope this is what we expect. > > Thanks and Regards, > Swapnil > > On Tue, Jul 21, 2015 at 4:27 AM, Imesh Gunaratne <im...@apache.org> wrote: > >> On Mon, Jul 20, 2015 at 9:20 PM, Swapnil Patil <swapnil.r...@gmail.com> >> wrote: >>> >>> >>> Though there was some time lag for the extension to get to know the >>> newly spawned instance. When a new instance is spawned the extension's >>> configure method got called but the topology did not have this new member. >>> This new member was visible in the next topology update. I believe this is >>> a known issue. I guess Asanka also faced similar issue for GCE extension. >>> Am I right, Asanka? >>> >>> >> Members are only added to the load balancer topology when they become >> active. Members in other states are not visible to the load balancer. >> >> On Mon, Jul 20, 2015 at 9:20 PM, Swapnil Patil <swapnil.r...@gmail.com> >> wrote: >> >>> Hi Lakmal, >>> >>> I tested the extension for scale up and scale down. And it did work as >>> expected. It attached the the newly spawned instances to the LB while >>> scaling up and detached the terminated instances from LB. >>> >>> Though there was some time lag for the extension to get to know the >>> newly spawned instance. When a new instance is spawned the extension's >>> configure method got called but the topology did not have this new member. >>> This new member was visible in the next topology update. I believe this is >>> a known issue. I guess Asanka also faced similar issue for GCE extension. >>> Am I right, Asanka? >>> >>> Thanks and Regards, >>> Swapnil >>> >>> On Mon, Jul 20, 2015 at 5:37 AM, Swapnil Patil <swapnil.r...@gmail.com> >>> wrote: >>> >>>> Thanks Lakmal! >>>> >>>> I have the logic in place to attach newly created instances to LB in >>>> case of scale up and same for scale down. But I have not tested it yet. >>>> That testing will be my next step. I am pretty sure that it will work but >>>> it is just that I need to verify it. >>>> >>>> I will get to know if any service interruption occurs in these cases >>>> when I test it. I will update the thread with my observations. >>>> >>>> Thanks and Regards, >>>> Swapnil >>>> >>>> On Mon, Jul 20, 2015 at 5:06 AM, Lakmal Warusawithana <lak...@wso2.com> >>>> wrote: >>>> >>>>> Great work Swapnil! >>>>> >>>>> Just for my clarification, I have few question. Say when cluster scale >>>>> up , does AWS load balancer extension attached the newly created instance >>>>> to LB? same like when scale down does it detached the deleted instance >>>>> from >>>>> LB? Also when attaching and detaching does any service interruption >>>>> occurs? >>>>> >>>>> thanks >>>>> >>>>> On Mon, Jul 20, 2015 at 10:11 AM, Swapnil Patil < >>>>> swapnil.r...@gmail.com> wrote: >>>>> >>>>>> Hi AIl, >>>>>> >>>>>> I have published screencast of AWS load balancer extension on >>>>>> YouTube. Here is the link : https://youtu.be/ZNl8JVB7xeU >>>>>> >>>>>> I would appreciate any suggestions. >>>>>> >>>>>> Thanks and Regards, >>>>>> Swapnil >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lakmal Warusawithana >>>>> Vice President, Apache Stratos >>>>> Director - Cloud Architecture; WSO2 Inc. >>>>> Mobile : +94714289692 >>>>> Blog : http://lakmalsview.blogspot.com/ >>>>> >>>>> >>>> >>> >> >> >> -- >> Imesh Gunaratne >> >> Senior Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
