Re: [Dev] [MB4] Removing Hazelcast dependency from common coordination tasks

[Indika Sampath]

+1 for removing Hazelcast from MB4 code base.

On Mon, Aug 21, 2017 at 12:58 PM, Asanka Abeyweera 
wrote:

> Hi all,
>
> We are still using Hazelcast for some common tasks even though we
> alternatively have the RDBMS based coordination implementation. I am
> planning to refactor code to remove those Hazelcast tasks in MB4.
>
> I could see that we are using Hazelcast for following tasks,
>
>- Hazelcast node addresses are maintained in Node details for
>consumption by an MBean service. Since we are planning to use REST services
>as an alternative to admin service, we can get rid of this. Additionally,
>in a non-Hazelcast environment, it does not make sense to maintain the
>Hazelcast node addresses.
>- To check if the node IDs are duplicated, a Hazelcase map is
>maintained. We can remove this when we use the RDBMS based coordination.
>- A unique ID generated using a Hazelcast ID generator is used as a
>parameter in generating cluster-wide unique IDs. Since we are focusing
>mainly on the 2 node HA deployment we do not need a cluster-wide unique
>message ID. If we need a cluster-wide unique ID we can later implement an
>algorithm on top of the RDBMS based coordination.
>
>
> WDYT?
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <+94%2071%20222%208648>
> Blog: a5anka.github.io
>
> 
>



-- 
Indika Sampath
Associate Technical Lead
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB4] Removing Hazelcast dependency from common coordination tasks

[Ramith Jayasinghe]

+1

On Mon, Aug 21, 2017 at 12:58 PM, Asanka Abeyweera 
wrote:

> Hi all,
>
> We are still using Hazelcast for some common tasks even though we
> alternatively have the RDBMS based coordination implementation. I am
> planning to refactor code to remove those Hazelcast tasks in MB4.
>
> I could see that we are using Hazelcast for following tasks,
>
>- Hazelcast node addresses are maintained in Node details for
>consumption by an MBean service. Since we are planning to use REST services
>as an alternative to admin service, we can get rid of this. Additionally,
>in a non-Hazelcast environment, it does not make sense to maintain the
>Hazelcast node addresses.
>- To check if the node IDs are duplicated, a Hazelcase map is
>maintained. We can remove this when we use the RDBMS based coordination.
>- A unique ID generated using a Hazelcast ID generator is used as a
>parameter in generating cluster-wide unique IDs. Since we are focusing
>mainly on the 2 node HA deployment we do not need a cluster-wide unique
>message ID. If we need a cluster-wide unique ID we can later implement an
>algorithm on top of the RDBMS based coordination.
>
>
> WDYT?
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <071%20222%208648>
> Blog: a5anka.github.io
>
> 
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MB4] Removing Hazelcast dependency from common coordination tasks

[Asanka Abeyweera]

Hi all,

We are still using Hazelcast for some common tasks even though we
alternatively have the RDBMS based coordination implementation. I am
planning to refactor code to remove those Hazelcast tasks in MB4.

I could see that we are using Hazelcast for following tasks,

   - Hazelcast node addresses are maintained in Node details for
   consumption by an MBean service. Since we are planning to use REST services
   as an alternative to admin service, we can get rid of this. Additionally,
   in a non-Hazelcast environment, it does not make sense to maintain the
   Hazelcast node addresses.
   - To check if the node IDs are duplicated, a Hazelcase map is
   maintained. We can remove this when we use the RDBMS based coordination.
   - A unique ID generated using a Hazelcast ID generator is used as a
   parameter in generating cluster-wide unique IDs. Since we are focusing
   mainly on the 2 node HA deployment we do not need a cluster-wide unique
   message ID. If we need a cluster-wide unique ID we can later implement an
   algorithm on top of the RDBMS based coordination.


WDYT?

-- 
Asanka Abeyweera
Senior Software Engineer
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev