Labkey 19.2 - Apache Tomcat 9.0.24

LabKey Trial Support
Labkey 19.2 - Apache Tomcat 9.0.24 Greg Otico  2019-09-11 12:51
Status: Closed
 

Hello Support,

We recently deployed Labkey 19.2 in a clustered Apache Tomcat 9.0.24 environment. When we make changes (ie. add projects) it only appears on one node and we need to restart the 2nd node for changes to appear on it. Is there some sore of cache setting that needs to be adjusted>

Please advise.

Thanks, Greg

 
 
Greg Otico responded:  2019-09-12 03:55

Labkey Support,

Do you have any information that can assist us in getting a clustered environment to work? We have 2 nodes and in order for changes to appear on the 2nd Tomcat node, we need to restart.

Thanks, Greg

 
Matthew Bellew responded:  2019-09-12 09:47

We have had customers successfully deploy LabKey in to a cluster in a fail-over configuration (only one LabKey active at a time). However, we do not support multiple instances of LabKey running against the same database server concurrently. As you guessed this is primarily due to aggressive caching in-memory caching.

 
Greg Otico responded:  2019-09-12 10:08

Thanks Matthew, is there a way to control caching (ie. timing to occur every minute or so) ?

 
Matthew Bellew responded:  2019-09-12 10:58

No there is not. You can clear the cache entirely from the site admin console which useful for testing/debugging and above-mentioned the fail over scenario. However, this will still not enable multiple LabKey servers running concurrently. That configuration is completely untested and unsupported.