[
https://issues.apache.org/jira/browse/HIVE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334030#comment-16334030
]
tartarus edited comment on HIVE-15631 at 1/22/18 11:09 AM:
-----------------------------------------------------------
[~prasanth_j]
Like this, I can filter the log according to sessionid
console:
*Hive Session ID = 61f5cb00-1f4a-4904-b2ef-4eeb8cdb2584*
hive.log:
*WARN [61f5cb00-1f4a-4904-b2ef-4eeb8cdb2584 main] conf.HiveConf: DEPRECATED:
hive.metastore.ds.retry.* *no longer has any effect. Use
hive.hmshandler.retry.* instead**
was (Author: tartarus):
[~prasanth_j]
Like this, I can filter the log according to sessionid
console:
*Hive Session ID = 61f5cb00-1f4a-4904-b2ef-4eeb8cdb2584*
hive.log:
*WARN [61f5cb00-1f4a-4904-b2ef-4eeb8cdb2584 main] conf.HiveConf: DEPRECATED:
hive.metastore.ds.retry.* no longer has any effect. Use
hive.hmshandler.retry.* instead*
> Optimize for hive client logs , you can filter the log for each session
> itself.
> -------------------------------------------------------------------------------
>
> Key: HIVE-15631
> URL: https://issues.apache.org/jira/browse/HIVE-15631
> Project: Hive
> Issue Type: Improvement
> Components: CLI, Clients, Hive
> Reporter: tartarus
> Assignee: tartarus
> Priority: Major
> Labels: pull-request-available
> Attachments: 0001-HIVE-15631.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We have several hadoop cluster, about 15 thousand nodes. Every day we use
> hive to submit above 100 thousand jobs.
> So we have a large file of hive logs on every client host every day, but i
> don not know the logs of my session submitted was which line.
> So i hope to print the hive.session.id on every line of logs, and then i
> could use grep to find the logs of my session submitted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
