You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "zhou xing (JIRA)" <ji...@apache.org> on 2016/05/06 05:05:12 UTC

[jira] [Commented] (MESOS-5060) Requesting /files/read.json with a negative length value causes subsequent /files requests to 404.

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

zhou xing commented on MESOS-5060:
----------------------------------

Added MESOS-5334 to further resolve the code logic issue.

> 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: zhou xing
>            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)