dlmarion commented on PR #5803: URL: https://github.com/apache/accumulo/pull/5803#issuecomment-3201863900
> I noticed that the resizePool() method resizes based on the maxThread property, and that when it's changed, the minThreads property is also changed to that new size in this code: Right, this was the logic that I was mentioning. IIRC we had to modify the core/max in a specific order based on the JDK internal code at that time. The current code just resizes based on the max size property IIRC because I don't think we resize based on the min/core size. You are trying to do something a little different than what we have done in the past, so you likely need a new method to resize the core and max independently, but might need to retain some of the logic from the existing resizePool method. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@accumulo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
