[ 
https://issues.apache.org/jira/browse/MESOS-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852679#comment-15852679
 ] 

Benjamin Hindman commented on MESOS-7036:
-----------------------------------------

For the short term I've replaced the use of {{RateLimiter}} with {{after}} in:

{code}
commit 56da6bbb4e84088cbb75d01a333605238ce83fc1
Author: Benjamin Hindman <[email protected]>
Date:   Sun Dec 18 18:49:29 2016 -0800

    Used process::after instead of process::RateLimiter.
    
    Review: https://reviews.apache.org/r/55322
{code}

If folks prefer we can close this JIRA and open another focused on the more 
general deadlock and the pattern/mechanisms we'd like to introduce to avoid it.

> Rate limiter deadlocks during IO Switchboard-related tests
> ----------------------------------------------------------
>
>                 Key: MESOS-7036
>                 URL: https://issues.apache.org/jira/browse/MESOS-7036
>             Project: Mesos
>          Issue Type: Bug
>          Components: test, tests
>         Environment: ASF CI
>            Reporter: Greg Mann
>            Priority: Critical
>              Labels: flaky, mesosphere
>         Attachments: AgentAPITest.LaunchNestedContainerSessionWithTTY.txt
>
>
> This has been observed a number of times recently on the ASF CI. While I 
> didn't look through every single failed test log, I've noticed the failure 
> occur during the following tests:
> {code}
> ContentType/AgentAPITest.LaunchNestedContainerSessionWithTTY/1
> ContentType/AgentAPITest.LaunchNestedContainerSessionWithTTY/0
> IOSwitchboardTest.ContainerAttachAfterSlaveRestart
> ContentType/AgentAPITest.LaunchNestedContainerSession/1
> ContentType/AgentAPITest.LaunchNestedContainerSessionDisconnected/1
> ContentType/AgentAPIStreamingTest.AttachContainerInput/0
> IOSwitchboardTest.ContainerAttach
> ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession/0
> {code}
> In all cases, we see the following:
> {code}
> **** DEADLOCK DETECTED! ****
> You are waiting on process __limiter__(518)@172.17.0.3:35849 that it is 
> currently executing.
> {code}
> Find attached an entire example log.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to