Hi Aparna, In new deployment we have 2 receiver/analyzer nodes and 2 dashboard nodes in the DMZ. There all receiver related artifacts, toolboxes and dashboard related artifacts can be committed from one of the receiver/analyzer node. Dashboard nodes are not supposed to commit anything.
Thanks. *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : [email protected] *Skype* : @manindae *Twitter* : @maninda On Wed, Oct 29, 2014 at 7:57 PM, Aparna Karunarathna <[email protected]> wrote: > Hi Anjana/KasunG/suho, > > According to the new BAM 2.5.0 deployment pattern [1] we have configured > the BAM cluster with 11 nodes(4 cassandra, 3 hadoop, 2 analyzer and 2 > receiver). Since BAM 2.5.0 is releasing with CEP features, we have to > enable the dep sync for receiver nodes as well. Therefore one of the > Analyzer/Receiver nodes were configured as RW nodes and other > analyzer/receiver nodes were configured as RO nodes and pointed to a single > svn repo. > > Toolboxes can be deployed to the Analyzer RW node and CEP input adapters > to the Receiver RW node. We have seen svn conflicts when both RW nodes were > trying to commit to svn repo. > > Therefore, how to configure the Dep Sync for Analyzer/Receiver nodes in > BAM 2.5.0 clustered setup? Please advice. > > [1] https://docs.wso2.com/display/CLUSTER420/Deploying+BAM+with+Puppet > > > Regards, > -- > *Aparna Karunarathna.* > > > *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
