[
https://issues.apache.org/jira/browse/HIVE-23555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118583#comment-17118583
]
Hive QA commented on HIVE-23555:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13004232/HIVE-23555.04.patch
{color:green}SUCCESS:{color} +1 due to 8 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17295 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/22666/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/22666/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-22666/
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 13004232 - PreCommit-HIVE-Build
> Cancel compaction jobs when hive.compactor.worker.timeout is reached
> --------------------------------------------------------------------
>
> Key: HIVE-23555
> URL: https://issues.apache.org/jira/browse/HIVE-23555
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Attachments: HIVE-23555.02.patch, HIVE-23555.03.patch,
> HIVE-23555.04.patch, HIVE-23555.patch
>
>
> Currently when a compactor worker thread is stuck, or working too long on a
> compaction the the initiator might decide to start a new compaction because
> of a timeout, but old worker might still wait for the results of the job.
> It would be good to cancel the worker as well after the timeout is reached
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
