We run multiple application pods on OpenShift(AWS) that talk to an external
mongo db cluster which spreads out in datacenters(not AWS).

During a deployment, it normally takes about 10 mins for "Apache Sling
Repository Startup Thread" to do its thing. What is it doing? Any idea what
it takes so long? Why is every application pod doing repository startup?

Do you recommend attaching a persistent volume to the application pods? Is
there a way for Sling to tell other pods there is no need to do repository
startup if it was done already?

-- 
Lisa Davidson, RHCE
Sr. Software Engineer
Red Hat, Inc.

Reply via email to