[
https://issues.apache.org/jira/browse/HIVE-16313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946955#comment-15946955
]
Peter Vary commented on HIVE-16313:
-----------------------------------
[~ychena]: The log messages are written out from Driver.tryAcquireCompileLock.
When the log level is DEBUG, then it will print out the message to the logs. If
we use BeeLine, these logs are diverted to the {{OperationLog}} as well by the
{{LogDivertAppender}}, so it will be printed to the output.
Above the DEBUG level logs, when we have to wait for the lock, we specifically
write that out to the {{OperationLog}} too.
{code}
// If the first shot fails, then we log the waiting messages.
if (LOG.isDebugEnabled()) {
LOG.debug("Waiting to acquire compile lock: " + command);
}
OperationLog ol = OperationLog.getCurrentOperationLog();
{code}
I was thinking about changing the Driver code, to remove the duplications, but
I decided against it since there are different configurations for the
{{LOG}}-s, and for the {{OperationLog}}, so this is the only way, that we can
be sure that the log is written.
> Flaky test: TestBeeLineDriver[drop_with_concurrency]
> ----------------------------------------------------
>
> Key: HIVE-16313
> URL: https://issues.apache.org/jira/browse/HIVE-16313
> Project: Hive
> Issue Type: Sub-task
> Components: Test
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: HIVE-16313.patch
>
>
> TestBeeLineDriver test become flaky:
> {code}
> 28a29 > Acquired the compile lock
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
