[
https://issues.apache.org/jira/browse/MESOS-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639361#comment-16639361
]
Alexander Rukletsov commented on MESOS-9274:
--------------------------------------------
*Backports to 1.7.1:*
{noformat}
830a7d53218ae472d10cf5733dab2c13600638b2
f8ba9e3f4fb1bb8fe7d0e35bd3d92696cb8381a7
{noformat}
*Backports to 1.6.2:*
{noformat}
6ec452b7ecaae63a1eb79416b58ac5916c3fff6c
e26e907ff72670877af6b7868634df335d04006d
{noformat}
These patches can't be back ported to 1.5.x because [the scheduler
library|https://github.com/apache/mesos/blob/ba960ed45e80119eadf398abd72609538fbc983e/include/mesos/v1/scheduler.hpp#L65]
does not provide {{call()}} method there, which [was
introduced|https://github.com/apache/mesos/commit/c39ef69514e57ca7c90e764a4a617abf88cd144f#diff-008387c75189aa7afcf0726f8d22530b]
in Mesos 1.6.0.
> v1 JAVA scheduler library can drop TEARDOWN upon destruction.
> -------------------------------------------------------------
>
> Key: MESOS-9274
> URL: https://issues.apache.org/jira/browse/MESOS-9274
> Project: Mesos
> Issue Type: Bug
> Components: java api, scheduler driver
> Reporter: Alexander Rukletsov
> Assignee: Alexander Rukletsov
> Priority: Major
> Labels: api, mesosphere, scheduler
> Fix For: 1.6.2, 1.7.1, 1.8.0
>
>
> Currently the v1 JAVA scheduler library neither ensures {{Call}} s are sent
> to the master nor waits for responses. This can be problematic if the library
> is destroyed (or garbage collected) right after sending a {{TEARDOWN}} call:
> destruction of the underlying {{Mesos}} actor races with sending the call.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
