Ma Jian created HUDI-7329:
-----------------------------
Summary: HUDI Experiences Significant Delays When Initializing
ServiceabilityAgentSupport with Velox Enabled
Key: HUDI-7329
URL: https://issues.apache.org/jira/browse/HUDI-7329
Project: Apache Hudi
Issue Type: Bug
Reporter: Ma Jian
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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
