Hi,
On Thu, Jan 9, 2014 at 11:58 AM, Udara Rathnayake <[email protected]> wrote: > Hi Malith, > > Thanks for your clarification. We haven't mentioned anything about > localMemberPort configuration, Is it ok to have different values for this > across nodes? > It's okay. You can use any valid port number for localMemberPort as long as that port is not being used by another process. > In my set-up I tried with 4000 across all nodes first and then with > different values. But I haven't noticed any difference. > > Please check my other question in-line. > > On Wed, Jan 8, 2014 at 4:57 PM, Malith Dhanushka <[email protected]> wrote: > >> >> >> >> On Wed, Jan 8, 2014 at 3:53 PM, Udara Rathnayake <[email protected]> wrote: >> >>> Hi all, >>> >>> Is it possible to use localMemberHost configuration for multicast data >>> analyzer clustering as mentioned here[1] under step 7? >>> >> > Is this(using hostname) the recommended way to configure localMemberHost? > Found that there is a known issue in Hazelcast WKA clustering and here is > the related public JIRA [3]. > There is an issue when using hostname and I didn't encounter any issues when using IP addresses. > But I'm not sure whether this can affect on multicast-clustering or not. > Any thoughts? > This may affect as the localMemberHost and localMemberPort are member properties and these are used for the network configuration in Hazelcast. The mcastBindAddress property is actually used in Axis2 Tribes clustering and the properties for Hazelcast are different. See [1]. Also I think it's better to use wka membership when configuring your analyzer nodes for clustering. [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0004/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/clustering/hazelcast/multicast/MulticastConstants.java > > [3]. https://wso2.org/jira/browse/CARBON-14573 > >> >> Yes it is. >> >> >>> What is the difference between localMemberHost and mcastBindAddress? >>> >> >> According to the doc[2] cluster can listen for point-to-point messages >> on the localMemberHost network interface while listening for multicast >> messages on the network interface bound to the mcastBindAddress. And I >> think mcastBindAddress is an optional parameter. >> >> [2]http://docs.wso2.org/display/CLUSTER420/Glossary >> >> Thanks >> >>> >>> [1]. >>> http://docs.wso2.org/display/CLUSTER420/Fully-Distributed%2C+High-Availability+BAM+Setup >>> >>> Regards, >>> UdaraR >>> -- >>> *Udara Rathnayake* >>> Software Engineer >>> WSO2 Inc. : http://wso2.com >>> >>> Mobile : +94 772207239 >>> Twitter : http://twitter.com/udarakr >>> Blog : http://udarakr.blogspot.com >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Malith Dhanushka >> Engineer - Data Technologies >> *WSO2, Inc. : wso2.com <http://wso2.com/>* >> *Mobile* : +94 716 506 693 >> > > > > -- > *Udara Rathnayake* > Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile : +94 772207239 > Twitter : http://twitter.com/udarakr > Blog : http://udarakr.blogspot.com > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
