On Thu, Sep 29, 2016 at 10:06 AM, Sidath Weerasinghe <sid...@wso2.com>
wrote:

> Hi all,
>
> In Andes client, I implemented a new initialContextFactory and inside
> that, I made an AMQP URL.
> Inside the Andes client, I called that web service to get the cluster node
> IP address and Port details. When calling web service it shuffles  the IP
> address and gives String to the client. Using this, create AMQP URL inside
> the Andes client, Other IPs put as a failover.
>
​What is the web service you called to get the all the members? Can this be
a single point of failure?

>
> The client can set failover values as properties.  Inside the new
> initialContextFactory, read those properties and set failover.
> "amqp://admin:admin@carbon/carbon?brokerlist='tcp://10.100.4.165:5672?
> *retries='10'&connectdelay='1000'*;tcp://10.100.4.166:5672?
> *retries='10'&connectdelay='1000''&failover='roundrobin?cyclecount='20'*'"
>
> Any ideas for this.
>
> On Thu, Sep 22, 2016 at 5:11 PM, Sidath Weerasinghe <sid...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> In MB, the user/developers having to manually list out the IPs in the
>> connection URL could be difficult. The change of IPs of the broker nodes
>> would require reconfiguring and restart the client applications connected
>> to it. I am implementing a way to dynamically detection the MB nodes in the
>> cluster and load balance through them.
>>
>> I got the IP address(all network interfaces) and AMQP port and store
>> database at cluster startup. When node shutdown that details are removed
>> from the database.
>> I wrote an admin service to get those database details at the carbon
>> business module.
>>
>> In andes client, I implemented a new initialContextFactory and inside
>> that, I made an AMQP URL. As a mock, I got the IP list from the file and
>> randomly select one of the IP and port and make AMPQ URL. Other IPs  put as
>> a fail-over. I tested it.
>>
>> *Work to be done*
>> I will call web service inside the andes client and get the IP and port
>> and resolve it according to the client network. After that get the correct
>> IP and the port.
>>
>>
>> --
>> Thank You,
>> Best Regards,
>>
>> Sidath Weerasinghe
>>
>>
>> *Intern*
>>
>> *WSO2, Inc. *
>>
>> *lean . enterprise . middleware *
>>
>>
>> *Mobile: +94719802550 <%2B94719802550>*
>>
>> *Email: *sid...@wso2.com
>>
>> Blog: https://medium.com/@sidath
>>
>> Linkedin: https://lk.linkedin.com/in/sidathweerasinghe
>>
>
>
>
> --
> Thank You,
> Best Regards,
>
> Sidath Weerasinghe
>
>
> *Intern*
>
> *WSO2, Inc. *
>
> *lean . enterprise . middleware *
>
>
> *Mobile: +94719802550 <%2B94719802550>*
>
> *Email: *sid...@wso2.com
>
> Blog: https://medium.com/@sidath
>
> Linkedin: https://lk.linkedin.com/in/sidathweerasinghe
>
> _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Best Regards,

Malaka Silva
Senior Technical Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
https://wso2.com/signature
http://www.wso2.com/about/team/malaka-silva/
<http://wso2.com/about/team/malaka-silva/>
https://store.wso2.com/store/

Don't make Trees rare, we should keep them with care
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to