Hi Théo, thanks. That's what I have suspected.
Cheers, Gin Best Wishes, Gintautas Sulskus On Sat, Oct 10, 2015 at 9:18 AM, Théo Chamley <theo...@mley.fr> wrote: > Hello, > > I can’t seem to find it in the documentation, but no, this is not the > behaviour of the FarmWarDeployer. > This component is triggered only by adding or removing an app, not by > adding or removing a node in the cluster. It will not sync automatically > the apps to your new node. > Two solutions: > * Make sure that your new node comes up with the apps already deployed. > * Once your new node has joined the cluster, redeploy the apps (a touch on > the war file should do it) cluster-wide. > > //Théo > > > On 10 Oct 2015, at 01:48, Gintautas Sulskus <gintautas.suls...@gmail.com> > wrote: > > > > Hi, > > > > suppose I have a Tomcat 8 cluster coordinated via multicast. > > If I understand it right, any newly started server will be picked up > > automatically and any down servers will eventually be dropped out from > the > > cluster. > > > > I was wondering, how does FarmWarDeployer cope with this dynamics? > > Say I have two Tomcat 8 servers T1 and T2 running some apps. Then, a > third > > server T3 joins the cluster. Does T3 get synced in terms of applications > or > > do I have to deploy these apps myself? > > > > I believe I have read somewhere in Tomcat documentation that this is the > > case. It was very laconic though. > > > > Thanks! > > > > Best Wishes, > > Gin > >