{"action":"created","issue":{"url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/387","repository_url":"https://api.github.com/repos/apache-spark-on-k8s/spark","labels_url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/387/labels{/name}","comments_url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/387/comments","events_url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/387/events","html_url":"https://github.com/apache-spark-on-k8s/spark/issues/387","id":244863846,"number":387,"title":"spark history server ","user":{"login":"luck02","id":364095,"avatar_url":"https://avatars0.githubusercontent.com/u/364095?v=4","gravatar_id":"","url":"https://api.github.com/users/luck02","html_url":"https://github.com/luck02","followers_url":"https://api.github.com/users/luck02/followers","following_url":"https://api.github.com/users/luck02/following{/other_user}","gists_url":"https://api.github.com/users/luck02/gists{/gist_id}","starred_url":"https://api.github.com/users/luck02/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/luck02/subscriptions","organizations_url":"https://api.github.com/users/luck02/orgs","repos_url":"https://api.github.com/users/luck02/repos","events_url":"https://api.github.com/users/luck02/events{/privacy}","received_events_url":"https://api.github.com/users/luck02/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-07-22T18:37:45Z","updated_at":"2017-08-25T04:00:11Z","closed_at":null,"body":"Wondering if anyone has considered this use case:\r\nhttps://spark.apache.org/docs/2.1.0/monitoring.html#viewing-after-the-fact\r\n\r\nPresumable you'd want to deploy a history server like the resource server or shuffle service.  And we'd want to have a way to configure jobs to leave their event logs somewhere.\r\n\r\nHas anyone thought about this, in an ideal world I'd like to contribute this.  \r\n\r\nThe history server is really quite important for the k8s / spark story as it looks like the intention is a short lived cluster / job.  So we'd need a way to inspect the UI after job has executed (and blown up).\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/comments/324818143","html_url":"https://github.com/apache-spark-on-k8s/spark/issues/387#issuecomment-324818143","issue_url":"https://api.github.com/repos/apache-spark-on-k8s/spark/issues/387","id":324818143,"user":{"login":"duyanghao","id":12867714,"avatar_url":"https://avatars2.githubusercontent.com/u/12867714?v=4","gravatar_id":"","url":"https://api.github.com/users/duyanghao","html_url":"https://github.com/duyanghao","followers_url":"https://api.github.com/users/duyanghao/followers","following_url":"https://api.github.com/users/duyanghao/following{/other_user}","gists_url":"https://api.github.com/users/duyanghao/gists{/gist_id}","starred_url":"https://api.github.com/users/duyanghao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/duyanghao/subscriptions","organizations_url":"https://api.github.com/users/duyanghao/orgs","repos_url":"https://api.github.com/users/duyanghao/repos","events_url":"https://api.github.com/users/duyanghao/events{/privacy}","received_events_url":"https://api.github.com/users/duyanghao/received_events","type":"User","site_admin":false},"created_at":"2017-08-25T04:00:11Z","updated_at":"2017-08-25T04:00:11Z","body":">>\r\nThat wouldn't work, unless that's running within the cluster. We need to write a deployment that launches the SHS within the cluster. Tracked in #387. Closing as dupe.\r\n\r\n@foxish i start SHS outside of k8s cluster,and it works without logs as i mention in this [issue]()."}}
{"actor":{"display_login":"duyanghao"}}