[ https://issues.apache.org/jira/browse/HIVE-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387956#comment-14387956 ]
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: https://issues.apache.org/jira/secure/attachment/12708295/HIVE-10128.02.patch {color:red}ERROR:{color} -1 due to 7 failed/errored test(s), 8692 tests executed *Failed tests:* {noformat} TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file org.apache.hadoop.hive.ql.exec.persistence.TestBytesBytesMultiHashMap.testExpand org.apache.hadoop.hive.ql.exec.persistence.TestBytesBytesMultiHashMap.testGetNonExistent org.apache.hadoop.hive.ql.exec.persistence.TestBytesBytesMultiHashMap.testPutGetMultiple org.apache.hadoop.hive.ql.exec.persistence.TestBytesBytesMultiHashMap.testPutGetOne org.apache.hadoop.hive.ql.exec.persistence.TestBytesBytesMultiHashMap.testPutWithFullMap org.apache.hive.jdbc.TestMultiSessionsHS2WithLocalClusterSpark.testSparkQuery {noformat} Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3212/testReport Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3212/console Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3212/ 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: 7 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12708295 - PreCommit-HIVE-TRUNK-Build > BytesBytesMultiHashMap does not allow concurrent read-only access > ----------------------------------------------------------------- > > Key: HIVE-10128 > URL: https://issues.apache.org/jira/browse/HIVE-10128 > 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 (v6.3.4#6332)