[
https://issues.apache.org/jira/browse/HIVE-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400559#comment-16400559
]
BELUGA BEHR commented on HIVE-18878:
------------------------------------
[~stakiar] I'm not sure how to quantify "a lot", but I just took a sample and
saw 25 instances over the course of several hours. This logging, I just don't
find useful from an operational standpoint. In general, I only need to know if
something went right, or went wrong, not "I am about to do XYZ...". In the
name of concise and efficient logging, this one should go.
> Lower MoveTask Lock Logging to Debug
> ------------------------------------
>
> Key: HIVE-18878
> URL: https://issues.apache.org/jira/browse/HIVE-18878
> Project: Hive
> Issue Type: Improvement
> Components: Locking
> Affects Versions: 3.0.0
> Reporter: BELUGA BEHR
> Assignee: Kryvenko Igor
> Priority: Minor
> Labels: noob
> Attachments: HIVE-18878.1.patch, HIVE-18878.patch
>
>
> https://github.com/apache/hive/blob/cbb9233a3b39ab8489d777fc76f0758c49b69bef/ql/src/java/org/apache/hadoop/hive/ql/exec/MoveTask.java#L233-L234
> {code}
> LOG.info("about to release lock for output: {} lock: {}", output,
> lock.getHiveLockObject().getName());
> try {
> lockMgr.unlock(lock);
> } catch (LockException le) {
> {code}
> Change this to _debug_ level logging. The lock manager's 'unlock' method
> should have additional logging available. Knowing that the unlock is about
> to take place is only helpful for debugging, not for normal operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
