We are running Appian as a multi-gateway environment. We've had a

timdw over 11 years ago

We are running Appian as a multi-gateway environment.

We've had a few growing pains getting this configured and running smoothly. I'd be interested in hearing from other multi-gateway installations about their experience.

In one situation, we were generating errors with our KDBs due to how we had checkpointing setup. Originally, we mistakenly ran the checkpoint-suite.sh script without any parameters and ran it on both servers creating contentions. We now have written a script that checkpoints each engine individually with a two minute pause between each. Further, this script is only executed on one of the servers in the cluster.

Another challenge we've had is with respect to our Unix mounts. We've setup a separate NFS on which we've placed _admin and the specified folders from system then pointed both servers to this central location. Our gateways, however, are on the same drive as the rest of the Appian & JBoss software. We've then...

Discussion posts and replies are publicly visible

Parents

0 timdw over 11 years ago

... setup up mounts on each server to point to the other server's gateways. I'm no Unix guru and was not a part of this setup / configuration. Unfortunately, due to how these mounts are defined, if we reboot both VMs simultaneously, we have issues with the mounts as they can't be created as the other server is not up. At this point our solution is to boot the VMs one at a time ensuring that the first has completed its boot up cycle before starting the second. How do you handle this contention?

What pitfalls have you encountered? What server maintenance best practices have you implemented?

Thanks in advance for sharing from your experience!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 timdw over 11 years ago

... setup up mounts on each server to point to the other server's gateways. I'm no Unix guru and was not a part of this setup / configuration. Unfortunately, due to how these mounts are defined, if we reboot both VMs simultaneously, we have issues with the mounts as they can't be created as the other server is not up. At this point our solution is to boot the VMs one at a time ensuring that the first has completed its boot up cycle before starting the second. How do you handle this contention?

What pitfalls have you encountered? What server maintenance best practices have you implemented?

Thanks in advance for sharing from your experience!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data