You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2016/05/17 01:52:12 UTC

[jira] [Resolved] (KYLIN-1319) Find a better way to check hadoop job status

     [ https://issues.apache.org/jira/browse/KYLIN-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhong Yanghong resolved KYLIN-1319.
-----------------------------------
    Resolution: Implemented

> 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
>            Reporter: liyang
>            Assignee: Zhong Yanghong
>              Labels: newbie
>         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)