Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi Tishan, Anuruddha and I went through the Siddhi-core 2.1.0 code and noticed that TimeBatchWindowProcessor class has the same issue in restoreState method [1]. What is the impact of this error "Syncing failed when becoming a Passive Node"? [1] http://svn.wso2.org/repos/wso2/carbon/platform/branc

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi Tishan, As discussed offline issue is with window.restoreState((Object[]) data[0]); > line. Underlying window implementation(SchedulerSiddhiQueue) is expecting > a object[] for its restore method and cast its first element > to LinkedBlockingQueue. But we are sending first element itself again

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi Anuruddha, As discussed offline issue is with window.restoreState((Object[]) data[0]); line. Underlying window implementation(SchedulerSiddhiQueue) is expecting a object[] for its restore method and cast its first element to LinkedBlockingQueue. But we are sending first element itself again aft

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

On Thu, Sep 17, 2015 at 9:44 AM, Sriskandarajah Suhothayan wrote: > have you properly migrated SecondDerivativeFinderWindowProcessor to new > siddhi version. the bug is there. > > I also doubt this, it looks like this error has been raised by the following method in SecondDerivativeFinderWindowP

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi All, I remote debugged this and found out why this is occurring. The issue is when we are building the Siddhi configuration We set 'DistributedProcessing' by checking whether ExecutionPlanConfiguration returns "true" for the property "siddhi.enable.distributed.processing". if (isDistributedPr

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

have you properly migrated SecondDerivativeFinderWindowProcessor to new siddhi version. the bug is there. Suho On Thu, Sep 17, 2015 at 9:32 AM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Ramindu, > > Please find the CEP artefacts that is being used [1]. > Please note that the nod

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi Ramindu, Please find the CEP artefacts that is being used [1]. Please note that the node starts first is not throwing any error. [1] https://drive.google.com/a/wso2.com/file/d/0Bw0NgSFZG5YkWUZybUoxbzM0TTg/view?usp=sharing

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

>From the logs it looks like its an issue in SecondDerivativeFinderWindowProcessor check the getting and restoring the state part. Suho On Wed, Sep 16, 2015 at 10:16 PM, Ramindu De Silva wrote: > Hi Anuruddha, > > Is it possible to send me the artefacts you used for this scenario, so > that i c

Re: [Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi Anuruddha, Is it possible to send me the artefacts you used for this scenario, so that i can reproduce and debug and see whats causing this issue. Best Regards, On Wed, Sep 16, 2015 at 7:30 PM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi, > > I created CEP HA cluster with Depl

[Dev] [CEP 3.1.0] Syncing failed when becoming a Passive Node for tenant

Hi, I created CEP HA cluster with Deployment for full-active-active mode as per [1]. I am seeing following error when starting the 2nd member. I have also attached execution plan [2]. What is causing this issue ? [2015-09-16 13:22:38,191] ERROR - {HAManager} Syncing failed when becoming a Passi