On Thu, Jan 17, 2019, 3:36 PM Mark Thomas <ma...@apache.org wrote: > On 17/01/2019 15:28, Tim K wrote: > > > With the DeltaManager, instead of it notifying all nodes when sessions > get > > established, is there a way for it to only share that single node's > > sessions during a shutdown event of that particular node? For example, > > node 1 of 8 has 5 sessions on it. When node 1 is shut down, only then > will > > it replicate those 5 sessions to the other 7 nodes... This would reduce > > the all-to-all traffic that would be occurring constantly but would put > > more weight on a shutdown event... Also, another wrinkle, the shutdown > port > > is disabled in server.xml for security reasons. > > None of the managers can be configured to replicate only on shutdown. > > The BackupManager is closer to the behaviour you describe. Note it is a > common misconception that in the BackupManager a single node acts as a > backup for all the other nodes. This is incorrect. Backups are > distributed on a round-robin basis between all other nodes. > > The shutdown port being disabled should be a non-issue. As long as you > kill -15 rather than kill -9 then you'll get a clean shutdown. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org
So to switch to Backup manager, just swap out the DeltaManager for it on each serve or just one? You're right, it does seem the backup manager was a single node, even after looking again at the documentation. Is the backup manager "battle tested" enough since the documentation was written? Is there less network traffic with backup manager? My nodes all have the same single app installed, I'm not sure what the advantage would be in using the backup manager.
