[
https://issues.apache.org/jira/browse/HIVE-20202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609419#comment-16609419
]
Hive QA commented on HIVE-20202:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12939040/HIVE-20202.8.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 14930 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.exec.spark.TestSparkSessionTimeout.testMultiSparkSessionTimeout
(batchId=245)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/13698/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13698/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13698/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12939040 - PreCommit-HIVE-Build
> Add profiler endpoint to HS2 and LLAP
> -------------------------------------
>
> Key: HIVE-20202
> URL: https://issues.apache.org/jira/browse/HIVE-20202
> Project: Hive
> Issue Type: New Feature
> Affects Versions: 4.0.0, 3.2.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Priority: Major
> Attachments: HIVE-20202.1.patch, HIVE-20202.2.patch,
> HIVE-20202.3.patch, HIVE-20202.4.patch, HIVE-20202.5.patch,
> HIVE-20202.6.patch, HIVE-20202.7.patch, HIVE-20202.8.patch
>
>
> Add a web endpoint for profiling based on async-profiler. This servlet should
> be added to httpserver so that HS2 and LLAP daemons can output flamegraphs
> when their /prof endpoint is hit. Since this will be based on
> [https://github.com/jvm-profiling-tools/async-profiler] heap allocation, lock
> contentions, HW counters etc. will also be supported in addition to cpu
> profiling. In most cases the profiling overhead is pretty low and is safe to
> run on production. More analysis on CPU and memory overhead here
> [https://github.com/jvm-profiling-tools/async-profiler/issues/14] and
> [https://github.com/jvm-profiling-tools/async-profiler/issues/131]
>
> For the impatient, here is the usage doc and the sample output
> [https://github.com/prasanthj/nightswatch/blob/master/README.md]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
