To add to Lasantha's comment on point 2 2) After starting the STORM cluster, CEP managers and CEP worker node, We couldn't see anything on the STORM UI under topology. Does that mean cluster is not setup correctly?
You can verify if the cluster has setup correctly by logging in to storm UI. You should be able to see the information of nimbus and all supervisors listed. And also please verify that the IP address of nimbus has been added to repository/conf/cep/storm/storm.yaml of CEP manager node. Thanks *,Sajith Ravindra* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273550 blog: http://sajithr.blogspot.com/ <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> On Tue, Aug 25, 2015 at 8:45 PM, Lasantha Fernando <[email protected]> wrote: > Hi Suho, > > Sure. Will do. > > @Sashika, can you share the event-processor.xml and the axis2.xml files of > your configuration? > > Also please find my comments inline regarding the queries raised above. > > > > On 25 August 2015 at 19:34, Sriskandarajah Suhothayan <[email protected]> > wrote: > >> Lasantha & Sajith please look into it, looks like there is a config >> issue. >> >> And also add this info the to docs so it will not be miss leading. >> >> Suho >> >> On Tue, Aug 25, 2015 at 8:55 AM, Sashika Wijesinghe <[email protected]> >> wrote: >> >>> Hi All, >>> >>> We have set up the distributed mode deployment for CEP using two CEP >>> managers and one CEP worker. but still we have some issues to get clarified. >>> >>> 1) When the worker node is started, we couldn't find any record in >>> manager logs whether the worker connected to CEP Manager or not. How to >>> verify whether worker is successfully connected with the storm and CEP >>> managers? >>> >> > You should be able to go to the execution plan listing page where a > 'Distributed Deployment Status' is shown which will give you an idea about > the status of the Storm topology as well as the inflow/outflow connections. > The CEP workers will simply talk to the CEP managers to get information > about Storm receiver spouts within the topology. Then the workers > themselves will establish the connections. You should see logs similar to > below when worker connects to Storm. > > [2015-08-25 20:38:58,221] INFO > {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener} > - [-1234:ExecutionPlan:CEPPublisher] Initializing storm output event > listener > [2015-08-25 20:38:58,266] INFO > {org.wso2.carbon.event.processor.manager.commons.transport.server.TCPEventServer} > - EventServer starting event listener on port 15001 > [2015-08-25 20:38:58,270] INFO > {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener} > - [-1234:ExecutionPlan:CEPPublisher] Registering output stream listener > for Siddhi stream : highCountStream > [2015-08-25 20:38:58,275] INFO > {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer > added to the junction. Stream:highCountStream:1.0.0 > [2015-08-25 20:38:58,271] INFO > {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener} > - [-1234:ExecutionPlan:CEPPublisher] Registering CEP publisher for > 10.100.0.75:15001 > [2015-08-25 20:38:58,299] INFO > {org.wso2.carbon.event.processor.common.util.AsyncEventPublisher} - > [-1234:ExecutionPlan:CEPReceiver] Requesting a StormReceiver for > 10.100.0.75 > [2015-08-25 20:38:58,301] INFO > {org.wso2.carbon.event.stream.core.internal.EventJunction} - Consumer > added to the junction. Stream:org.wso2.test.stream:1.0.0 > [2015-08-25 20:38:58,314] INFO > {org.wso2.carbon.event.processor.core.EventProcessorDeployer} - Execution > plan is deployed successfully and in active state : ExecutionPlan > [2015-08-25 20:38:58,352] INFO > {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener} > - [-1234:ExecutionPlan:CEPPublisher] Successfully registered CEP publisher > for 10.100.0.75:15001 > [2015-08-25 20:38:58,352] INFO > {org.wso2.carbon.event.processor.common.util.AsyncEventPublisher} - > [-1234:ExecutionPlan:CEPReceiver] Retrieved StormReceiver at > 10.100.0.75:15000 from storm manager service at 10.100.0.75:8904 > [2015-08-25 20:38:58,377] INFO > {org.wso2.carbon.event.processor.manager.commons.transport.client.TCPEventPublisher} > - Connecting to 10.100.0.75:15000 > [2015-08-25 20:38:58,384] INFO > {org.wso2.carbon.event.processor.common.util.AsyncEventPublisher} - > [-1234:ExecutionPlan:CEPReceiver] Connected to StormReceiver at > 10.100.0.75:15000 for the Stream(s) testStream, > > > >> >>> 2) After starting the STORM cluster, CEP managers and CEP worker node, >>> We couldn't see anything on the STORM UI under topology. Does that mean >>> cluster is not setup correctly? >>> >> > A storm topology would not appear unless it has been submitted by creating > an execution plan. Did you create an execution plan? If so, can you share > the execution plan? > > >> >>> 3) How multiple CEP workers used in production setup? >>> As we understood, CEP workers handle all the communication and >>> processing within CEP. If there are two worker nodes, how those two workers >>> manage the work among them? Are we going to keep one worker node in active >>> mode and the other node in passive mode? >>> >> > Workers would simply be scaled up as necessary and the load balancing > would happen from the client side of CEP. i.e. When sending events to CEP, > you can use databridge agents to load balance to CEP nodes so the events > are distributed. The workers won't have a special active/passive mode under > normal configuration. > > Please let us know if there were any doc issues or misleading > configuration elements that could be improved. > > Thanks, > Lasantha > > >> >>> >>> Thanks and Regards, >>> -- >>> >>> *Sashika WijesingheSoftware Engineer - QA Team* >>> Mobile : +94 (0) 774537487 >>> [email protected] >>> >> >> >> >> -- >> >> *S. Suhothayan* >> Technical Lead & Team Lead of WSO2 Complex Event Processor >> *WSO2 Inc. *http://wso2.com >> * <http://wso2.com/>* >> lean . enterprise . middleware >> >> >> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >> > > > > -- > *Lasantha Fernando* > Senior Software Engineer - Data Technologies Team > WSO2 Inc. http://wso2.com > > email: [email protected] > mobile: (+94) 71 5247551 >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
