[
https://issues.apache.org/jira/browse/KYLIN-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443369#comment-15443369
]
hongbin ma commented on KYLIN-1319:
-----------------------------------
KYLIN-1319 makes KYLIN-1014 deprecated
> Find a better way to check hadoop job status
> --------------------------------------------
>
> Key: KYLIN-1319
> URL: https://issues.apache.org/jira/browse/KYLIN-1319
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
> Reporter: liyang
> Assignee: Zhong Yanghong
> Labels: newbie
> Fix For: v1.5.3
>
> Attachments:
> Find_better_way_of_checking_hadoop_job_status_by_YarnClient_master.patch,
> Find_better_way_of_checking_hadoop_job_status_via_job_API_master.patch
>
>
> Currently Kylin retrieves jobs status via a resource manager web service like
> {code}https://<your_rm_server>:<port>/ws/v1/cluster/apps/${job_id}?anonymous=true{code}
> It is not most robust. Some user does not have
> "yarn.resourcemanager.webapp.address" set in yarm-site.xml, then get status
> will fail out-of-box. They have to set a Kylin property
> "kylin.job.yarn.app.rest.check.status.url" to overcome, which is not user
> friendly.
> Kerberos authentication might cause problem too if security is enabled.
> Is there a more robust way to check job status? Via Job API?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
