Hi Vanjikumaran, Yes we have tested that scenario in the EC2 environment and worked.
Best Regards, On Thu, Jul 7, 2016 at 12:47 AM, Vanjikumaran Sivajothy <[email protected]> wrote: > In the most cases in enterprise deployment, mostly we uses the > VIP/HostName compare IP. In that case does it support HostName/VIP? > > > > On Wed, Jul 6, 2016 at 7:46 AM, Ramindu De Silva <[email protected]> > wrote: > >> Hi Isuru, >> >> Please find the explanations inline. >> >> In a two node HA cluster, in the eventSync/hostName configuration >> (event-processor.xml), do we need to provide the own host IP? If so, how >> does each nodes discover each other for event synchronization purpose? For >> what exact purpose this eventSync configuration is used? >> >> The provided host IP will be saved in the Hazelcast map after getting the >> server's state (passive [1] / active [2] ). So the other members which are >> in the cluster can get the relevant configuration using the passive key and >> active key. >> >> >> If we add a presenter node in addition to the two worker nodes, I assume >> we should point to the presenter node from the both worker nodes. As per >> the configuration, seems this is a TCP level connection. Why do we need a >> TCP connection to the presenter? >> >> In, HA configured serves, each and every server contains the same >> artifacts, even the presenter node. But the presenter node only publishes >> the output which has been already processed by the active node which is >> received using the tcp connection [3]. >> >> FYI, the active node also sends the events to the passing node using the >> tcp connection, and the events will be processed in parallel but the >> passive node will drop the events from publishing or sending to the >> presenter node (if available). >> >> 1. >> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-processor-manager/org.wso2.carbon.event.processor.manager.core/src/main/java/org/wso2/carbon/event/processor/manager/core/internal/HAManager.java#L259 >> >> >> 2. >> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-processor-manager/org.wso2.carbon.event.processor.manager.core/src/main/java/org/wso2/carbon/event/processor/manager/core/internal/HAManager.java#L233 >> >> 3. >> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-processor-manager/org.wso2.carbon.event.processor.manager.core/src/main/java/org/wso2/carbon/event/processor/manager/core/internal/EventHandler.java#L161 >> >> >> Best Regards, >> >> On Wed, Jul 6, 2016 at 4:49 PM, Isuru Haththotuwa <[email protected]> >> wrote: >> >>> += wso2-dev list >>> <https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0#ClusteringCEP4.0.0-Highavailabilitydeployment> >>> >>> On Wed, Jul 6, 2016 at 4:34 PM, Isuru Haththotuwa <[email protected]> >>> wrote: >>> >>>> Hi CEP team, >>>> >>>> I'm going through [1] to understand the CEP HA deployment. Have a few >>>> doubts to get clarified: >>>> >>>> >>>> 1. In a two node HA cluster, in the eventSync/hostName >>>> configuration (event-processor.xml), do we need to provide the own host >>>> IP? >>>> If so, how does each nodes discover each other for event synchronization >>>> purpose? For what exact purpose this eventSync configuration is used? >>>> 2. If we add a presenter node in addition to the two worker nodes, >>>> I assume we should point to the presenter node from the both worker >>>> nodes. >>>> As per the configuration, seems this is a TCP level connection. Why do >>>> we >>>> need a TCP connection to the presenter? >>>> >>>> Missed the link: >>> >>> [1]. >>> https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0#ClusteringCEP4.0.0-Highavailabilitydeployment >>> >>>> >>>> -- >>>> Thanks and Regards, >>>> >>>> Isuru H. >>>> +94 716 358 048* <http://wso2.com/>* >>>> >>>> >>>> >>> >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ramindu De Silva* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> email: [email protected] <[email protected]> >> mob: +94 772339350 >> mob: +94 719678895 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Vanjikumaran Sivajothy > *Associate Technical Lead* > *WSO2 Inc. http://wso2.com <http://wso2.com/>* > *+1-925-464-6816* > [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: Twitter] > <https://twitter.com/vanjikumaran> [image: LinkedIn] > <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: > Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] > <http://www.slideshare.net/vanjikumaran> > > This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may > have received this communication in error, please reply to the > sender indicating that fact and delete the copy you received and in > addition, you should not print, copy, re-transmit, disseminate, or > otherwise use the information contained in this communication. > Internet communications cannot be guaranteed to be timely, secure, error > or virus-free. The sender does not accept liability for any errors > or omissions > -- *Ramindu De Silva* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware email: [email protected] <[email protected]> mob: +94 772339350 mob: +94 719678895
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
