Thanks for the prompt response, Gokul. On Thu, Jul 19, 2018 at 11:57 AM Gokul Balakrishnan <[email protected]> wrote:
> That's right. If you're not using Spark, you can ignore > spark-defaults.conf. The nodes will still need to be Hazelcast clustered > however. > > On Thu, 19 Jul 2018 at 13:47, Shazni Nazeer <[email protected]> wrote: > >> Thanks, Gokul. >> >> If I get it right, I need to worry about spark-defaults.conf only if I >> have batch analytics in place, right? Otherwise, is it sufficient to >> configure the event-processor.xml HA mode? >> >> On Thu, Jul 19, 2018 at 11:43 AM Gokul Balakrishnan <[email protected]> >> wrote: >> >>> Hi Shazni, >>> >>> If you need no Spark functionality, you can skip setting up the Spark >>> cluster, and concentrate only on the real-time aspects. This way, both >>> Spark nodes will simply act as independent processing units. However, this >>> is not a feasible model of operation if/when you need batch analytics >>> capabilities. >>> >>> The same applies to indexing (interactive analytics) as well. >>> >>> To go one step further, you can start up both DAS nodes as Receiver >>> nodes. When this is done, only the event receivers and the Siddhi runtimes >>> will be active, and the Spark- & Indexing- related bundles will not be >>> active at all. Again, if you need to do any batch analytics or indexing, >>> this mode will not be sufficient. >>> >>> Best, >>> >>> On Thu, 19 Jul 2018 at 13:36, Shazni Nazeer <[email protected]> wrote: >>> >>>> I want to configure minimum HA between two DAS nodes. I only have CEP >>>> artifacts in the DAS. Is it necessary to do spark related configurations as >>>> is mentioned in the following doc in that case? Is it fine to skip that >>>> configuration since I do not have any batch scripts? >>>> >>>> [1] >>>> https://docs.wso2.com/display/DAS320/Configuring+a+Minimum+High+Availability+Cluster >>>> >>>> -- >>>> Shazni Nazeer >>>> >>>> Mob : +94 777737331 >>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>> >>>> Blogs : >>>> >>>> https://medium.com/@mshazninazeer >>>> http://shazninazeer.blogspot.com >>>> >>>> <http://wso2.com/signature> >>>> >>> >>> >>> -- >>> Gokul Balakrishnan >>> Associate Lead Solutions Engineer >>> WSO2, Inc. | http://wso2.com >>> M +94 77 593 5789 | P +94 11 214 5345 >>> >>> >>> <http://wso2.com/signature> >>> >> >> >> -- >> Shazni Nazeer >> >> Mob : +94 777737331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> >> Blogs : >> >> https://medium.com/@mshazninazeer >> http://shazninazeer.blogspot.com >> >> <http://wso2.com/signature> >> > > > -- > Gokul Balakrishnan > Associate Lead Solutions Engineer > WSO2, Inc. | http://wso2.com > M +94 77 593 5789 | P +94 11 214 5345 > > > <http://wso2.com/signature> > -- Shazni Nazeer Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blogs : https://medium.com/@mshazninazeer http://shazninazeer.blogspot.com <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
