You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The profiler jar is stored in s3 (mybucket/profilers/jvm-profiler-1.0.0.jar). While bootstrapping my core and master nodes, I run the following bootstrap script
But I am unable to see the profiling related output in the logs (checked both stdout and stderr logs for all containers). Is the parameter ignored ? Am I missing something ? Is there something else I could check to see why this parameter is being ignored ?
The text was updated successfully, but these errors were encountered:
I am trying to use uber jvm profiler to profile my spark application (spark 2.4, running on emr 5.21)
Following is my cluster configuration
The profiler jar is stored in s3 (
mybucket/profilers/jvm-profiler-1.0.0.jar
). While bootstrapping my core and master nodes, I run the following bootstrap scriptI submit my emr step as follows
But I am unable to see the profiling related output in the logs (checked both stdout and stderr logs for all containers). Is the parameter ignored ? Am I missing something ? Is there something else I could check to see why this parameter is being ignored ?
The text was updated successfully, but these errors were encountered: