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 2015/11/11 18:19:12 UTC
[jira] [Commented] (SLIDER-978) revisit why
OutstandingRequest.buildContainerRequest() sets label==null on a placed
request
[ https://issues.apache.org/jira/browse/SLIDER-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000713#comment-15000713 ]
Steve Loughran commented on SLIDER-978:
---------------------------------------
and update {{TestRoleHistoryOutstandingRequestTracker.testRequestLabelledPlacement()}} as appropriate
> revisit why OutstandingRequest.buildContainerRequest() sets label==null on a placed request
> -------------------------------------------------------------------------------------------
>
> Key: SLIDER-978
> URL: https://issues.apache.org/jira/browse/SLIDER-978
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster
> Affects Versions: Slider 0.81
> Reporter: Steve Loughran
> Fix For: Slider 0.90
>
>
> {{revisit why OutstandingRequest.buildContainerRequest() }} always leaves the label field unset when creating its placed request, setting it only when escalating.
> Is there a reason for this? If not, set it always
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)