You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/12/15 15:27:14 UTC

[jira] [Resolved] (SLIDER-724) Implement OfflineFilter to return 503 "unavailable", for AM bootstrap

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

Steve Loughran resolved SLIDER-724.
-----------------------------------
    Resolution: Won't Fix

Not fixing this. Although a filter has been written, wiring it up via the YARN helper classes is trickier. It turns out to be easier to move the web app startup until after all state has built

Filter class {{org.apache.slider.server.appmaster.web.utils.OfflineFilter}} is where the source can be found

> Implement OfflineFilter to return 503 "unavailable", for AM bootstrap
> ---------------------------------------------------------------------
>
>                 Key: SLIDER-724
>                 URL: https://issues.apache.org/jira/browse/SLIDER-724
>             Project: Slider
>          Issue Type: Sub-task
>          Components: Web & REST
>    Affects Versions: Slider 0.60
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: Slider 0.70
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Add a simple Web filter which can be turned offline/online, setting it offline at startup.
> This avoids any problems with the REST APIs being invoked before the AM is completely initiated. We have seen this on GET operations; once other verbs are supported this move from being a minor issue to a danger.



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