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

Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:27 UTC

[jira] [Issue Comment Deleted] (MESOS-6373) Add the ability to not accept any connections from a client.

     [ https://issues.apache.org/jira/browse/MESOS-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated MESOS-6373:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Add the ability to not accept any connections from a client.
> ------------------------------------------------------------
>
>                 Key: MESOS-6373
>                 URL: https://issues.apache.org/jira/browse/MESOS-6373
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Anand Mazumdar
>            Priority: Major
>              Labels: integration, mesosphere
>
> Similar to the old {{DROP_MESSAGES}} abstraction allowing us to drop all messages from a client, we need a way to drop all incoming connection requests from a client. When running our tests, we initialize the libprocess instance once. When we notice a disconnection via the {{Connection}} abstraction, we immediately reconnect back due to being able to initiate a connection with the running libprocess instance. 
> Use Cases: 
> - Upon using the mock executor instance, we are never able to test if the recovery timeout expired due to the executor being able to reconnect with the agent immediately upon a disconnection since the libprocess instance running the tests is always alive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)