[
https://issues.apache.org/jira/browse/MESOS-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated MESOS-9210:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> Mesos v1 scheduler library does not properly handle SUBSCRIBE retries
> ---------------------------------------------------------------------
>
> Key: MESOS-9210
> URL: https://issues.apache.org/jira/browse/MESOS-9210
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.5.1, 1.6.1, 1.7.0
> Reporter: Vinod Kone
> Assignee: Till Toenshoff
> Priority: Major
> Labels: integration, mesosphere
> Fix For: 1.5.3, 1.6.2, 1.7.2, 1.8.0
>
>
> After the authentication related refactor done as part of
> [https://reviews.apache.org/r/62594/], the state of the scheduler is checked
> in `send`
> ([https://github.com/apache/mesos/blob/master/src/scheduler/scheduler.cpp#L234)]
> but it is changed in `_send`
> ([https://github.com/apache/mesos/blob/master/src/scheduler/scheduler.cpp#L234).]
> As a result, we can have 2 SUBSCRIBE calls in flight at the same time on the
> same connection! This is not good and not spec compliant of a HTTP client
> that is expecting a streaming response.
> We need to fix the library to either drop the retried SUBSCRIBE call if one
> is in progress (as it was before the refactor) or close the old connection
> and start a new connection to send the retried SUBSCRIBE call.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
