[
https://issues.apache.org/jira/browse/HIVE-27511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-27511:
--------------------------------
Description:
When investigating TezAM OOM issues, a common problem is a huge conf. In this
we usually do the following:
1. ask for heapdump
2. analyze heapdump, and finally find huge UserPayload, which is binary form
3. deserialize userpayload
4. looks for configuration properties in payload to blame
5. figure out how to reduce the payload
I think with a handy configuration insight log message in HS2, we need to do
only 5) (as 1) 2) 3) 4) can be complicated)
was:
When investigating TezAM OOM issues, a common problem is a huge conf. In this
we usually do the following:
1. ask for heapdump
2. analyze heapdump, and find big UserPayload
3. looks for configuration properties in payload to blame
4. figure out how to reduce the payload
I think with a handy confuguration insight log message in HS2, we need to do
only 4) (as 1) 2) 3) can be complicated)
> Print Tez processor payload insights
> ------------------------------------
>
> Key: HIVE-27511
> URL: https://issues.apache.org/jira/browse/HIVE-27511
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
>
> When investigating TezAM OOM issues, a common problem is a huge conf. In this
> we usually do the following:
> 1. ask for heapdump
> 2. analyze heapdump, and finally find huge UserPayload, which is binary form
> 3. deserialize userpayload
> 4. looks for configuration properties in payload to blame
> 5. figure out how to reduce the payload
> I think with a handy configuration insight log message in HS2, we need to do
> only 5) (as 1) 2) 3) 4) can be complicated)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
