hudi-bot opened a new issue, #16377:
URL: https://github.com/apache/hudi/issues/16377
The current version of HUDI, when Velox (a C++ component) is enabled, uses
ObjectSizeCalculator.getObjectSize, which triggers the initialization of
ServiceabilityAgentSupport (in singleton mode, initialization occurs on the
first call). During this process, the execution of the needSudo method takes
approximately 50 seconds. If we restart a pod with Spark each time, it results
in a significant delay, which is a critical issue. Although it's possible to
bypass this by setting the JVM parameter -Djol.skipHotspotSAAttach=true, this
workaround requires additional configuration to restore normal operation. Is
this still considered an unexpected behavior?
Here's the private constructor for ServiceabilityAgentSupport:
{code:java}
private ServiceabilityAgentSupport() {
processId = getCurrentProcId();
agentStyle = senseAgentStyle();
sudoRequired = needSudo(agentStyle);
}
{code}
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-7329
- Type: Bug
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
