You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2019/01/30 05:20:00 UTC
[jira] [Commented] (MESOS-9210) Mesos v1 scheduler library does not
properly handle SUBSCRIBE retries
[ https://issues.apache.org/jira/browse/MESOS-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755697#comment-16755697 ]
Till Toenshoff commented on MESOS-9210:
---------------------------------------
master:
{noformat}
commit a5b9fcafbdf8663707e19c818be8a2da1eff8622 (HEAD -> master, origin/master, origin/HEAD)
Author: Till Toenshoff <to...@me.com>
Date: Wed Jan 30 05:37:17 2019 +0100
Fixed scheduler library on multiple SUBSCRIBE requests per connection.
The HTTP scheduler API dictates that on a single connection, the
scheduler may only send a single SUBSCRIBE request. Due to recent
authentication related changes, this contract got broken. This patch
restores the contract and adds a test validating that the library is
enforcing it.
Review: https://reviews.apache.org/r/69839/{noformat}
> 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
>
> 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)