Hi Andrés, In your earlier query, it seems that you have a sequence with two predicates running on different threads/nodes. In such a case, synching between the two threads can be non-trivial AFAIK.
However, you can try to scale first for other usecases (other than patterns, sequences). Different queries can be scaled in pipeline fashion, and also partitioning the input stream to scale might be another option. We are currently writing Siddhi 3.0.0 with more support for distributed cases. You can find the siddhi-3.0.0 branch at [1]. Please consider this as still 'Work in Progress'. However, let me dig deeper into your usecase and get back to you on how to tackle scalability on your usecase. [1] https://github.com/wso2-dev/siddhi/tree/Siddhi-3.0.0 Thanks, Lasantha On 3 October 2014 12:57, andresgomez92 <ago...@redborder.net> wrote: > Hi Lasantha, > > I have changed my storm topology. Now, all stream go to the same > siddhiManager instance and all queries works fine. > > But now, I only have 1 instance of siddhiManager without distributed > processing ... How can I get scalability??? > > > Thanks, > > Andrés > > > > ----- > -- > Andres Gomez > Developer at Eneo Tecnologia. > Website: http://redborder.net > LinkedIn: http://lnkd.in/sHnbJe > > -- > View this message in context: > http://wso2-oxygen-tank.10903.n7.nabble.com/siddhi-v2-2-0-SNAPSHOT-stop-calling-callbacks-after-few-seconds-tp103254p104350.html > Sent from the WSO2 Development mailing list archive at Nabble.com. > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev