[
https://issues.apache.org/jira/browse/HIVE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159266#comment-14159266
]
Hive QA commented on HIVE-8258:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12672875/HIVE-8258.3.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6541 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.txn.compactor.TestCleaner.partitionNotBlockedBySubsequentLock
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1116/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1116/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1116/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
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: 12672875
> Compactor cleaners can be starved on a busy table or partition.
> ---------------------------------------------------------------
>
> Key: HIVE-8258
> URL: https://issues.apache.org/jira/browse/HIVE-8258
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 0.13.1
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Critical
> Fix For: 0.14.0
>
> Attachments: HIVE-8258.2.patch, HIVE-8258.3.patch, HIVE-8258.patch
>
>
> Currently the cleaning thread in the compactor does not run on a table or
> partition while any locks are held on this partition. This leaves it open to
> starvation in the case of a busy table or partition. It only needs to wait
> until all locks on the table/partition at the time of the compaction have
> expired. Any jobs initiated after that (and thus any locks obtained) will be
> for the new versions of the files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
