2019年2月12日(火) 1:28 Tim K <tim.k.5...@gmail.com>: > On Fri, Jan 18, 2019, 12:44 PM Tim K <tim.k.5...@gmail.com> wrote: > > > On Fri, Jan 18, 2019 at 11:05 AM Christopher Schultz > > <ch...@christopherschultz.net> wrote: > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > > > > > Tim, > > > > > > On 1/18/19 06:38, Tim K wrote: > > > > 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. > > > > > > If you think you can help clarify the documentation, patches are of > > > course always welcome. > > > > > > > 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. > > > > > > I definitely wouldn't bring two down simultaneously if your can avoid > > > it. The cluster needs time to re-stabalize after the loss of a member, > > > meaning that new backup nodes must be selected for each session and > > > then the sessions must be transmitted to those backups nodes. If you > > > have small amounts of data in the sessions, this will probably be > > > fairly fast. If you have lots of data or a very busy network, it will > > > take longer. > > > > > > I would recommend setting-up a scenario (even in production) where you > > > intentionally disable a node in the cluster and watch to see how long > > > the cluster takes to re-stabalize. I think you'll learn a lot from > > > that exercise and it will help you plan for scheduled maintenance and > > > downtime. > > > > > > - -chris > > > > Is there a way to tell which server was assigned as the primary and > > backup roles? > > > > When I stop a member, is it this line which would tell me how long it > > took to sync up the sessions? > > Relocation of map entries was complete in [X] ms. > > > > Another question, I'm using the StaticMembershipService; do I need to > > define a LocalMember for each of my nodes or is that optional/assumed? > > > > Also, I recall reading something about the uniqueId might not really > > be used? Do I need to set that for each member? > > > > > I'm noticing my SSO cookie is being removed when I force myself to another > node. Is this a bug? > > > Are you using SSO(org.apache.catalina.authenticator.SingleSignOn)? DeltaManager/BackupManager replicate sessions. They do not replicate SSO entries.
If you want to replicate SSO Entry in cluster, you can use ClusterSingleSignOn. http://tomcat.apache.org/tomcat-9.0-doc/config/cluster-valve.html#org.apache.catalina.ha.authenticator.ClusterSingleSignOn -- Keiichi.Fujino