@ Isuru and Mohan - Thanks for the detailed information. @ Mohan, In the event receivers in DAS nodes, "event duplicated in cluster" property is set to "false". Therefore as you suggested I will configure load balancing or fail over cluster for analytics.
Regards, Sashika On Tue, Aug 23, 2016 at 1:13 AM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > > > On Tue, Aug 23, 2016 at 12:56 AM, Isuru Perera <isu...@wso2.com> wrote: > >> Hi, >> >> Do you need to publish data to multiple receiver nodes? You should be >> able to use multiple Receiver URLs. Metrics uses the Data Publisher API. >> Please check [1]. >> >> I think it's better to ask from DAS team. >> >> [1] https://docs.wso2.com/display/CEP420/Setting+up+Multi+Receiv >> er+and+Load+Balancing+Data+Agent >> > > +1.. > > @Sashika, how did you configured the event receiver in DAS side ? what is > the value for "events duplicated in cluster" property ? Based on that > property you have to configure DAS urls.. If this property is true then you > have to use option [1] > <https://docs.wso2.com/display/CEP420/Setting+up+Multi+Receiver+and+Load+Balancing+Data+Agent#SettingupMultiReceiverandLoadBalancingDataAgent-Sendingalltheeventstoseveralreceiversscenario2> > .. If this property is false then you can use load balancing or fail over > options which send events only to one node at a time.. > > Thanks, > Mohan > > >> >> >> On Mon, Aug 22, 2016 at 8:45 PM, Sashika Wijesinghe <sash...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> I have a requirement to connect Analytics cluster with the MB cluster >>> (MB 3.2.0 M2). >>> >>> To connect a single analytics node with MB 3.2.0 pack, there is a >>> configuration [1] in the metrics.xml file to provide the data receiver URL >>> of the analytics node. >>> When Configuring analytics cluster, I have used the minimum HA >>> deployment [2]. May I know how to configure the two analytics data receiver >>> nodes with MB to publish stats? >>> >>> [1] >>> <DAS> >>> <Enabled>true</Enabled> >>> <!-- Source of Metrics, which will be used to >>> identify each metric sent in the streams --> >>> <!-- Commented to use the hostname >>> <Source>Carbon</Source> >>> --> >>> <!-- Polling Period in seconds. >>> This is the period for polling metrics from the metric >>> registry and >>> sending events via the Data Publisher --> >>> <PollingPeriod>60</PollingPeriod> >>> <!-- The type used with Data Publisher --> >>> <Type>thrift</Type> >>> <!-- Data Receiver URL used by the Data Publisher --> >>> <ReceiverURL>tcp://localhost:7612</ReceiverURL> >>> <!-- Authentication URL for the Data Publisher --> >>> <!-- <AuthURL>ssl://localhost:7711</AuthURL> --> >>> <Username>admin</Username> >>> <Password>admin</Password> >>> <!-- Path for Data Agent Configuration --> >>> <DataAgentConfigPath>repository/conf/data-bridge/data-agent- >>> config.xml</DataAgentConfigPath> >>> </DAS> >>> >>> [2] https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Av >>> ailability+Deployment+-+DAS+3.0.1 >>> >>> Thanks >>> >>> -- >>> >>> *Sashika WijesingheSoftware Engineer - QA Team* >>> Mobile : +94 (0) 774537487 >>> sash...@wso2.com >>> >> >> >> >> -- >> Isuru Perera >> Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about> >> > > > > -- > *V. Mohanadarshan* > *Associate Tech Lead,* > *Data Technologies Team,* > *WSO2, Inc. http://wso2.com <http://wso2.com> * > *lean.enterprise.middleware.* > > email: mo...@wso2.com > phone:(+94) 771117673 > -- *Sashika WijesingheSoftware Engineer - QA Team* Mobile : +94 (0) 774537487 sash...@wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
