Encountered an issue where our instance start times vary depending on if the box running the instance is being restarted or not.
If the instance is stopped and then started without a reboot, our start time is around ~8 minutes
If the instance is stopped, a reboot of the box is performed, and then the instance is started after the box reboots our start time is around an hour(!).
Can anyone explain this behavior, and possibly how to alleviate this (if even possible)? We have a theory that some of the stuff is being stored in residual memory... but not certain of this yet.
Solved! Go to Solution.
Views
Replies
Total Likes
It various from case to case. Please get a couple of thread dumps when taking longer time, analzing it will give you a clue. Or you can file daycare ticket with all the logs and thread dump will analyze if you are not familar with thead dump analysis. Couple of scenario where I come across was Firewall (+ proxy) rules taking a while to make port open, Index merge was blocking other threads....
Views
Replies
Total Likes
It various from case to case. Please get a couple of thread dumps when taking longer time, analzing it will give you a clue. Or you can file daycare ticket with all the logs and thread dump will analyze if you are not familar with thead dump analysis. Couple of scenario where I come across was Firewall (+ proxy) rules taking a while to make port open, Index merge was blocking other threads....
Views
Replies
Total Likes
I've encountered this with 5.6.1 as well. The initial startup will take upwards of 20 minutes, with restarts (without system reboot) starting in 1-2 minutes.
Views
Replies
Total Likes
For this intial problem - the best route is to get the thread dumps that Sham asked for. Then open a ticket so Sham can explore exactly what is going on. That is why i closed thread. Next step is to explore with Sham.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies