[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3570:
--
Story Points: 8 (was: 5)
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere, newbie
> Fix For: 0.28.0
>
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3570:
--
Story Points: 5 (was: 3)
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman updated MESOS-3570:
Sprint: Mesosphere Sprint 27, Mesosphere Sprint 28, Mesosphere Sprint 29
(was: Mesosphere Sprint 27, Mesosphere Sprint 28)
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3570:
--
Shepherd: Vinod Kone
Assignee: Anand Mazumdar (was: Vinod Kone)
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-3570:
-
Sprint: Mesosphere Sprint 27, Mesosphere Sprint 28 (was: Mesosphere Sprint
27)
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Vinod Kone
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3570) Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3570:
--
Sprint: Mesosphere Sprint 27
Story Points: 3
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
>
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Vinod Kone
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
