Hi, As I can remember, when implementing the COORDINATOR_NODE_DETAILS_MAP map, we wanted to keep them separated for readability purposes. I think these two can be merged.
Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +94777688882 On Fri, Jul 17, 2015 at 10:38 AM, Asanka Abeyweera <[email protected]> wrote: > Hi, > > We are currently using following two hazelcast maps to store coordinator > node details. > > 1. THRIFT_SERVER_DETAILS_MAP - This is used by the thrift client to get > coordinators IP and port. > > 2. COORDINATOR_NODE_DETAILS_MAP - This is used to show the coordinator > node details in the management console. > > Can't we use a single hazelcast for these two purposes? > > [1] > https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/wso2/andes/server/cluster/coordination/CoordinationConstants.java > > -- > Asanka Abeyweera > Software Engineer > WSO2 Inc. > > Phone: +94 712228648 > Blog: a5anka.github.io >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
