aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "alexius ludeman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-955) more minimal http url to determine aurora leader
Date Wed, 03 Dec 2014 00:55:12 GMT

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

alexius ludeman commented on AURORA-955:
----------------------------------------

Erik, I believe it behaves this way now.

not leader
```
% curl -D - -s -k http://localhost:8081/cron
HTTP/1.1 302 Found
Location: http://leaderhost:8081/cron
Content-Length: 0
Server: Jetty(7.6.15.v20140411)
```

leader
```
% curl -D - -s -k http://localhost:8081/cron
HTTP/1.1 200 OK
Content-Type: application/json
Vary: Accept-Encoding
Transfer-Encoding: chunked
Server: Jetty(7.6.15.v20140411)

{"scheduled":{}}%
```

> more minimal http url to determine aurora leader
> ------------------------------------------------
>
>                 Key: AURORA-955
>                 URL: https://issues.apache.org/jira/browse/AURORA-955
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: alexius ludeman
>            Priority: Minor
>
> it'd be nicer if there was a /leader which is http response 200 for leader, and non-200
for not.
> or maybe add additional body content to /health to indicate leader or "not leader"
> Right now the best solution is to parse the contents of /var for "framework_registered
1" or "scheduler_lifecycle_ACTIVE 1"
> the html body of /vars is ~50k.
> or if you fetch /scheduler and look for a redirect.



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

Mime
View raw message