There was a bug where coordinator was trying to be come coordinator again
and failing, fixed and gave a patch to Lasindu

Suho

- Sent from phone -
On Jul 28, 2015 10:55 AM, "Sajith Ravindra" <saji...@wso2.com> wrote:

> Hi Imesh,
>
> We select coordinator among managers.
>
> 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 Mon, Jul 27, 2015 at 4:37 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Hi Suho,
>>
>> Do we select a coordinator within the manager nodes or is it just the
>> client that decides which manager to talk to?
>>
>> Thanks
>>
>> On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan <s...@wso2.com
>> > wrote:
>>
>>> CEP Managers are must for Strom based coordination, so use the CEP
>>> Managers to be the carbon cluster as well-known members, else it does not
>>> make sense for CEP deployment. We have also done the testing like that.
>>>
>>> Regards
>>> Suho
>>>
>>> On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana <lak...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana <lak...@wso2.com>
>>>> wrote:
>>>>
>>>>> +1 Azeez
>>>>>
>>>>
>>>> [I mean adding Azeez into the loop]
>>>>
>>>>
>>>>>
>>>>> On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith <lasi...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> We are having a clustered deployment of CEP 400 Beta in Stratos
>>>>>> 4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
>>>>>> clustering, I'm using 'Stratos Membership scheme' [1] which considers all
>>>>>> the members in the carbon cluster as well-known members. I have done CEP
>>>>>> Distributed deployment according to [3][4].
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> When CEP workers start up, I can see the following log [2] in worker
>>>>>> nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
>>>>>> restarted, the error goes away(Workers can connect to CEP Manager).
>>>>>> According to above membership scheme, any of the CEP workers/managers
>>>>>> can be the hazelcast coordinator. *Does CEP requires a member who is
>>>>>> both CEP manager as well as a hazelcast coordinator to be elected as the
>>>>>> Storm manager? *
>>>>>> Should CEP workers be always non-wka? How can we overcome this issue?
>>>>>>
>>>>>> [1] [Architecture] Stratos Membership Scheme for Automatically
>>>>>> Discovering Carbon Instances in a Carbon Cluster
>>>>>>
>>>>>> [2]
>>>>>> TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher 
>>>>>> with
>>>>>> current manager. Retrying after 5000ms
>>>>>> TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
>>>>>> for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
>>>>>> manager
>>>>>> NotStormManagerException(message:10.244.28.23:8904 not a storm
>>>>>> manager)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
>>>>>> at
>>>>>> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
>>>>>> for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
>>>>>> manager
>>>>>> NotStormManagerException(message:10.244.3.29:8904 not a storm
>>>>>> manager)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
>>>>>> at
>>>>>> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher 
>>>>>> with
>>>>>> current manager. Retrying after 5000ms
>>>>>> TID: [-1] [] [2015-07-27 04:51:21,892] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
>>>>>> for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
>>>>>> manager
>>>>>> NotStormManagerException(message:10.244.28.23:8904 not a storm
>>>>>> manager)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
>>>>>> at
>>>>>> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> TID: [-1] [] [2015-07-27 04:51:21,895] ERROR
>>>>>> {org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
>>>>>> -  [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
>>>>>> for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
>>>>>> manager
>>>>>> NotStormManagerException(message:10.244.3.29:8904 not a storm
>>>>>> manager)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
>>>>>> at
>>>>>> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
>>>>>> at
>>>>>> org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>
>>>>>> [3] https://docs.wso2.com/display/CEP400/Clustered+Deployment
>>>>>> [4]
>>>>>> https://docs.wso2.com/display/CEP400/Configuring+WSO2+CEP+to+Run+with+Apache+Storm
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> --
>>>>>> *Lasindu Charith*
>>>>>> Software Engineer, WSO2 Inc.
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> Mobile: +94714427192 | Web: blog.lasindu.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lakmal Warusawithana
>>>>> Vice President, Apache Stratos
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>> Mobile : +94714289692
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Lakmal Warusawithana
>>>> Vice President, Apache Stratos
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>> Mobile : +94714289692
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *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>*
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to