I'm running YouTrack 2017.1 on a Centos 7.3 server. The YouTrack server is configured to start automatically on server restarts using the method recommended in the documentation under the "YouTrack JAR as a Service on Linux" method.
This mostly works, but it has a significant limitation in that it only partially starts the server, so the first few clients just get server timeouts when they try to connect.
When I boot the server and let things settle down, the youtrack process shows about 1min:20sec of CPU time (from top):
1854 youtrack 20 0 3965488 499008 13888 S 0.0 25.3 1:20.22 java
When you try to connect to the server, the first 2-3 connections time out, and eventually the server stabilizes showing about 3 minutes of CPU time:
1854 youtrack 20 0 4105056 715396 13072 S 0.0 36.2 3:13.35 java
So for the first ~2 minutes after the first HTTP connection after rebooting a server, you can't actually access it, which causes a number of our REST API calls into the server to fail. Now every time we reboot a server with YouTrack we need to ask the admin to refresh the YouTrack page a few times to get it to fully start up, but this seems like a silly thing to need to do .. can I change something in the config so it will start up properly on it's own?