[jira] [Resolved] (AURORA-1621) Support redirect to leading scheduler host

[Ashwin Murthy (JIRA)]

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

Ashwin Murthy resolved AURORA-1621.
---
Resolution: Duplicate

Dupe of https://issues.apache.org/jira/browse/AURORA-1493

> Support redirect to leading scheduler host
> --
>
> Key: AURORA-1621
> URL: https://issues.apache.org/jira/browse/AURORA-1621
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Ashwin Murthy
>Assignee: Ashwin Murthy
>Priority: Minor
>  Labels: features, uber
>
> Support a health endpoint that returns 200 if the host corresponds to the one 
> of the leading scheduler. If not, return 500. This allows support for 
> redirect to the leading scheduler



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

[jira] [Commented] (AURORA-1493) create ELB-friendly endpoint to detect leading scheduler

[Ashwin Murthy (JIRA)]

[ 
https://issues.apache.org/jira/browse/AURORA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157429#comment-15157429
 ] 

Ashwin Murthy commented on AURORA-1493:
---

Brian, from your description of the issue above, it seems that support for http 
redirect to leading scheduler is already present? Is that true? I understand 
that for non routable ensemble instances, this doesnt work 

> 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-1621) Support redirect to leading scheduler host

[Ashwin Murthy (JIRA)]

[ 
https://issues.apache.org/jira/browse/AURORA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157420#comment-15157420
 ] 

Ashwin Murthy commented on AURORA-1621:
---

https://issues.apache.org/jira/browse/AURORA-1493, mentions that the web UI
redirects to the leading scheduler. Is this support already present in
aurora code base?

I do agree that we can close my JIRA as dupe.

On Mon, Feb 22, 2016 at 9:54 AM, Joshua Cohen (JIRA) 



> Support redirect to leading scheduler host
> --
>
> Key: AURORA-1621
> URL: https://issues.apache.org/jira/browse/AURORA-1621
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Ashwin Murthy
>Assignee: Ashwin Murthy
>Priority: Minor
>  Labels: features, uber
>
> Support a health endpoint that returns 200 if the host corresponds to the one 
> of the leading scheduler. If not, return 500. This allows support for 
> redirect to the leading scheduler



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

[jira] [Commented] (AURORA-1621) Support redirect to leading scheduler host

[Joshua Cohen (JIRA)]

[ 
https://issues.apache.org/jira/browse/AURORA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157379#comment-15157379
 ] 

Joshua Cohen commented on AURORA-1621:
--

This seems like it's potentially a dupe of 
https://issues.apache.org/jira/browse/AURORA-1493, [~ashwinm_uber] do you 
agree? If so, can we close this ticket in favor of that one?

> Support redirect to leading scheduler host
> --
>
> Key: AURORA-1621
> URL: https://issues.apache.org/jira/browse/AURORA-1621
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Ashwin Murthy
>Assignee: Ashwin Murthy
>Priority: Minor
>  Labels: features, uber
>
> Support a health endpoint that returns 200 if the host corresponds to the one 
> of the leading scheduler. If not, return 500. This allows support for 
> redirect to the leading scheduler



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

[jira] [Updated] (AURORA-1621) Support redirect to leading scheduler host

[Chris Lambert (JIRA)]

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

Chris Lambert updated AURORA-1621:
--
Labels: features uber  (was: features)

> Support redirect to leading scheduler host
> --
>
> Key: AURORA-1621
> URL: https://issues.apache.org/jira/browse/AURORA-1621
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Ashwin Murthy
>Assignee: Ashwin Murthy
>Priority: Minor
>  Labels: features, uber
>
> Support a health endpoint that returns 200 if the host corresponds to the one 
> of the leading scheduler. If not, return 500. This allows support for 
> redirect to the leading scheduler



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

[jira] [Updated] (AURORA-1621) Support redirect to leading scheduler host

[Chris Lambert (JIRA)]

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

Chris Lambert updated AURORA-1621:
--
Component/s: (was: Service Discovery)
 Scheduler

> Support redirect to leading scheduler host
> --
>
> Key: AURORA-1621
> URL: https://issues.apache.org/jira/browse/AURORA-1621
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Ashwin Murthy
>Assignee: Ashwin Murthy
>Priority: Minor
>  Labels: features
>
> Support a health endpoint that returns 200 if the host corresponds to the one 
> of the leading scheduler. If not, return 500. This allows support for 
> redirect to the leading scheduler



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

[jira] [Created] (AURORA-1621) Support redirect to leading scheduler host

[Ashwin Murthy (JIRA)]

Ashwin Murthy created AURORA-1621:
-

 Summary: Support redirect to leading scheduler host
 Key: AURORA-1621
 URL: https://issues.apache.org/jira/browse/AURORA-1621
 Project: Aurora
  Issue Type: Task
  Components: Service Discovery
Reporter: Ashwin Murthy
Assignee: Ashwin Murthy
Priority: Minor


Support a health endpoint that returns 200 if the host corresponds to the one 
of the leading scheduler. If not, return 500. This allows support for redirect 
to the leading scheduler



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