hi @jasontedor, as you closed the issue on git, I was wondering if you could elaborate more here on why you are sure this isn't an issue in elastic?
The reason I'm asking is that we are currently in an ongoing investigation with Azure which already opened a ticket to canonical about this issue. When Azure discuss this issue with canonical they were insisting that the issue is with the java process (in this case elastic) that is not releasing the CPU.
If you could provide us any information or guide us to find proof that the issue is not an elastic issue it will help expedite the process of finding the root cause.
Thanks for your help!
Yoni.