hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10128) BytesBytesMultiHashMap does not allow concurrent read-only access
Date Tue, 31 Mar 2015 04:26:53 GMT


Hive QA commented on HIVE-10128:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 7 failed/errored test(s), 8692 tests executed
*Failed tests:*
TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file

Test results:
Console output:
Test logs:

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: 7 tests failed

This message is automatically generated.

ATTACHMENT ID: 12708295 - PreCommit-HIVE-TRUNK-Build

> BytesBytesMultiHashMap does not allow concurrent read-only access
> -----------------------------------------------------------------
>                 Key: HIVE-10128
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gopal V
>            Assignee: Sergey Shelukhin
>             Fix For: llap
>         Attachments: HIVE-10128.01.patch, HIVE-10128.02.patch, HIVE-10128.patch, hashmap-after.png,
hashmap-sync-source.png, hashmap-sync.png
> The multi-threaded performance takes a serious hit when LLAP shares hashtables between
the probe threads running in parallel. 
> !hashmap-sync.png!
> This is an explicit synchronized block inside ReusableRowContainer which triggers this
particular pattern.
> !hashmap-sync-source.png!
> Looking deeper into the code, the synchronization seems to be caused due to the fact
that WriteBuffers.setReadPoint modifies the otherwise read-only hashtable.
> To generate this sort of result, run LLAP at a WARN log-level, to avoid all the log synchronization
that otherwise affects the thread sync.

This message was sent by Atlassian JIRA

View raw message