On Fri, Jan 18, 2019, 4:55 AM Mark Thomas <ma...@apache.org wrote: > On 18/01/2019 01:40, Tim K wrote: > > 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? > > All of them. > > > 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? > > Yes. > > > Is there less network traffic with backup manager? > > Yes. > > > My nodes all have the > > same single app installed, I'm not sure what the advantage would be in > > using the backup manager. > > Less network traffic. > > See: > https://www.youtube.com/watch?v=6LoAdy9-jBI > > particularly from around 29:30 > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org
Thanks for this. The video helps explain it a bit better than the documentation. So I set it up with a backup manager instead of the delta manager, changing the channelSendOptions to 6 for the cluster. >From a maintenance standpoint, what is the best way to stop/start the nodes without losing sessions; one at a time, letting it fully come up before moving on to the next one (like a ripple restart)? I presume you don't want too many nodes to be down at a single time.
