[
https://issues.apache.org/jira/browse/HIVE-20041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530096#comment-16530096
]
Gopal V commented on HIVE-20041:
--------------------------------
[~abstractdog]: the cache entry needs to print itself a little differently -
this needs to have a CacheEntry#<n> where <n> is the identityHashCode of the
object.
The part I'm debugging right now is entirely about the same query with diff
cache entries (all PENDING), so I need to also know which one each thread is
pending on, though the .toString() of all of them are identical.
> ResultsCache: Improve loggng for concurrent queries
> ---------------------------------------------------
>
> Key: HIVE-20041
> URL: https://issues.apache.org/jira/browse/HIVE-20041
> Project: Hive
> Issue Type: Improvement
> Components: Diagnosability
> Reporter: Gopal V
> Assignee: Laszlo Bodor
> Priority: Minor
> Attachments: HIVE-20041.01.patch
>
>
> The logging for QueryResultsCache ends up printing information without
> context, like
> {code}
> 2018-06-30T17:48:45,502 INFO [HiveServer2-Background-Pool: Thread-166]
> results.QueryResultsCache: Waiting on pending cacheEntry
> {code}
> {code}
> 2018-06-30T17:50:17,963 INFO [HiveServer2-Background-Pool: Thread-145]
> ql.Driver: savedToCache: true
> {code}
> The previous lines for this are in DEBUG level, so the logging ends up being
> useless at INFO level to debug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
