mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Mann (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-5060) Requesting /files/read.json with a negative length value causes subsequent /files requests to 404.
Date Fri, 08 Apr 2016 20:33:25 GMT

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

Greg Mann reassigned MESOS-5060:
--------------------------------

    Assignee: Greg Mann  (was: zhou xing)

> Requesting /files/read.json with a negative length value causes subsequent /files requests
to 404.
> --------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-5060
>                 URL: https://issues.apache.org/jira/browse/MESOS-5060
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>         Environment: Mesos 0.23.0 on CentOS 6, also Mesos 0.28.0 on OSX
>            Reporter: Tom Petr
>            Assignee: Greg Mann
>            Priority: Minor
>             Fix For: 0.29.0
>
>
> I accidentally hit a slave's /files/read.json endpoint with a negative length (ex. http://hostname:5051/files/read.json?path=XXX&offset=0&length=-100).
The HTTP request timed out after 30 seconds with nothing relevant in the slave logs, and subsequent
calls to any of the /files endpoints on that slave immediately returned a HTTP 404 response.
We ultimately got things working again by restarting the mesos-slave process (checkpointing
FTW!), but it'd be wise to guard against negative lengths on the slave's end too.



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

Mime
View raw message