[jira] [Commented] (AURORA-1493) create ELB-friendly endpoint to detect leading scheduler
[ https://issues.apache.org/jira/browse/AURORA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746036#comment-14746036 ] brian wickman commented on AURORA-1493: --- it ignores anything but 200 OK. a redirect wouldn't really be useful (most likely the host/ip being redirected is an internal host/ip) but i think the LB would just ignore that. > create ELB-friendly endpoint to detect leading scheduler > > > Key: AURORA-1493 > URL: https://issues.apache.org/jira/browse/AURORA-1493 > Project: Aurora > Issue Type: Task > Components: Scheduler, Usability >Reporter: brian wickman > > iiuc hitting the web ui for non-leading schedulers redirects to the leader. > this doesn't really help the members of the ensemble are not publicly > routable. > if there was a /leader endpoint that returned "200 OK" if it is leader and > some 3xx/4xx code if not, then it would be easier to configure an ELB to > route traffic to the correct leader, simplifying the use of aurora in an AWS > deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1485) TaskConfig default container value breaks client library generation for GO
[
https://issues.apache.org/jira/browse/AURORA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746019#comment-14746019
]
Jake Farrell commented on AURORA-1485:
--
This was raised in THRIFT-3051 for the default union values not working,
working on a patch for that now. As for this patch I plan to change it to now
make the TaskConfig.Container be a required value, but will leave the default
value { "mesos": {} } in place.
> TaskConfig default container value breaks client library generation for GO
> --
>
> Key: AURORA-1485
> URL: https://issues.apache.org/jira/browse/AURORA-1485
> Project: Aurora
> Issue Type: Story
> Components: Client
>Reporter: Jake Farrell
>Assignee: Jake Farrell
> Fix For: 0.10.0
>
>
> When generating the client api library for go the default containerizer used
> as a hack for AURORA-1185 breaks and causes the client lib to not be
> generated correctly. The default value for the optional field `container = {
> "mesos": {} }` is not necessary as it is defaulted in java code on the api
> side.
> Tracking this down it looks like the default value was a last minute addition
> based on some review comments and is not necessary or used anywhere. Removing
> the default value does not impact anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
