You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "tartarus (JIRA)" <ji...@apache.org> on 2017/01/15 08:22:26 UTC
[jira] [Updated] (HIVE-15631) Optimize for hive client logs , you
can filter the log for each session itself.
[ https://issues.apache.org/jira/browse/HIVE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
tartarus updated HIVE-15631:
----------------------------
Description:
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.
was: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.
> 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
> 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
(v6.3.4#6332)