You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Goden Yao (JIRA)" <ji...@apache.org> on 2016/08/01 17:40:20 UTC
[jira] [Updated] (HAWQ-970) Provide More Accurate Information When
LibYARN Meets an Exception
[ https://issues.apache.org/jira/browse/HAWQ-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Goden Yao updated HAWQ-970:
---------------------------
Fix Version/s: backlog
> Provide More Accurate Information When LibYARN Meets an Exception
> -----------------------------------------------------------------
>
> Key: HAWQ-970
> URL: https://issues.apache.org/jira/browse/HAWQ-970
> Project: Apache HAWQ
> Issue Type: Bug
> Components: libyarn
> Reporter: Lin Wen
> Assignee: Lei Chang
> Fix For: backlog
>
>
> Sometimes when an exception happens in libyarn, the log information is not accurate enough. For example, below is an exception related to kerberos ticket expiration, but we can't know from this log.
> {code}
> 2016-07-06 01:47:51.945902 BST,,,p182375,th140327040,,,,0,con4,,seg-10000,,,,,"WARNING","01000","YARN mode resource broker failed to get container report. LibYarnClient::getContainerReports, Catch the Exception:YarnIOException: Unexpected exception: when calling ApplicationCl
> ientProtocol::getContainers in /data1/pulse2-agent/agents/agent1/work/LIBYARN-main-opt/rhel5_x86_64/src/libyarnserver/ApplicationClientProtocol.cpp: 195",,,,,,,0,,"resourcebroker_LIBYARN_proc.c",1748,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)