You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Jonathan Maron (JIRA)" <ji...@apache.org> on 2015/10/14 16:38:05 UTC

[jira] [Comment Edited] (SLIDER-945) build up history of request/release/failures for each component and serve in the REST API (and web UI?)

    [ https://issues.apache.org/jira/browse/SLIDER-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957024#comment-14957024 ] 

Jonathan Maron edited comment on SLIDER-945 at 10/14/15 2:37 PM:
-----------------------------------------------------------------

Is there any overlap here with a potential integration with the YARN Timeline Server?  


was (Author: jmaron):
Is there any overlap here with a potential integration with ATS?  

> build up history of request/release/failures for each component and serve in the REST API (and web UI?)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SLIDER-945
>                 URL: https://issues.apache.org/jira/browse/SLIDER-945
>             Project: Slider
>          Issue Type: Sub-task
>          Components: appmaster, Web & REST
>    Affects Versions: Slider 0.80
>            Reporter: Steve Loughran
>             Fix For: Slider 0.90
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> For testing things like SLIDER-82, it'd be good to have a history where we can list events for each component (e.g. requested containers, released containers, failed container, escalation). This would be a structured log which could be viewed in the REST API for each component, and parseable for the test runner to get a view of what happened to get the cluster to its current state;
> Could be good as an HTML view too, so you can see what's going on. We do end up looking in the AM logs for this kind of information, after all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)