[
https://issues.apache.org/jira/browse/KYLIN-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262650#comment-15262650
]
Richard Calaba edited comment on KYLIN-1319 at 4/28/16 6:12 PM:
----------------------------------------------------------------
Hello, is this bug still actively tracked ??? We are running into it again and
again on our HA MapR configuration.
I am suggesting resolution strategy:
1) Enable configuration property kylin.job.yarn.app.rest.check.status.url to be
able to contain multiple URLs (comma separated); In case the WS call fails the
engine uses round-robin approach to start asking 2nd WS URL - if this replies
back - then it keeps using 2nd URL for the Job Status WS calls ; if it fails it
starts looking into 3rd one ... and so on ...
2) Utilize zookeeper to get info where is the active Job Status WS located
was (Author: [email protected]):
Hello, is this bug still actively tracked ??? We are running into it again and
again on our HA MapR configuration.
I am suggesting resolution strategy:
1) Enable configuration property yarn.resourcemanager.webapp.address to be able
to contain multiple URLs (comma separated); In case the WS call fails the
engine uses round-robin approach to start asking 2nd WS URL - if this replies
back - then it keeps using 2nd URL for the Job Status WS calls ; if it fails it
starts looking into 3rd one ... and so on ...
2) Utilize zookeeper to get info where is the active Job Status WS located
> 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
>
> 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)
