*Puppet Server Version: Latest
*OS Name/Version: Any
The JRuby pool used by Puppet Server and PE Orchestrator has a lock functionality that is used, notably by Code Manager, to drain in-flight requests in order to gain exclusive access to file resources used by JRuby.
The lifecycle of requesting, acquiring, and releasing this lock has a critical impact on JRuby availability and thus on service performance. The following messages around the lock lifecycle logged at DEBUG level:
Due to the critical nature of this workflow, these messages should be logged at INFO level to facilitate post-mortem debugging.