[ https://issues.apache.org/jira/browse/HIVE-22906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040175#comment-17040175 ]
Hive QA commented on HIVE-22906: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12993795/HIVE-22906.1.patch {color:red}ERROR:{color} -1 due to no test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 18026 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/20730/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20730/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20730/ 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: 12993795 - PreCommit-HIVE-Build > Redundant checkLock Mutex blocks concurrent Lock requests > --------------------------------------------------------- > > Key: HIVE-22906 > URL: https://issues.apache.org/jira/browse/HIVE-22906 > Project: Hive > Issue Type: Improvement > Components: Locking > Reporter: Denys Kuzmenko > Assignee: Denys Kuzmenko > Priority: Major > Attachments: HIVE-22906.1.patch > > > enqueueLocks is already serialising locks creation via (SELECT NL_NEXT FROM > NEXT_LOCK_ID FOR UPDATE). Requested locks would be assigned 'W' state. > checkLock is iterating over the sorted set of conflicting locks below current > EXT_LOCK_ID. It does handle the situation when there is conflicting lock with > lower ID in 'W' state - lock request would be denied and retried later. -- This message was sent by Atlassian Jira (v8.3.4#803005)