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

Alexander Rukletsov commented on MESOS-5878:
--------------------------------------------

Though the log is a bit confusing (the await future failure is right at the 
top), it seems that this future failure is related to the update registry 
failure (at the bottom):
{noformat}
I0721 05:03:51.022830 28189 replica.cpp:712] Persisted action at 13
I0721 05:03:51.022821 28178 leveldb.cpp:341] Persisting action (286 bytes) to 
leveldb took 23.227367ms
E0721 05:04:00.954085 28181 registrar.cpp:531] Registrar aborting: Failed to 
update 'registry': Failed to perform store within 10secs
I0721 05:04:33.684514 28178 replica.cpp:712] Persisted action at 13
{noformat}

If this hypothesis is true, than the test failure was most probably caused by 
the slow CI. Closing it for now; it the issue pops up again, we will 
investigate further.

> Strict/RegistrarTest.UpdateQuota/0 is flaky
> -------------------------------------------
>
>                 Key: MESOS-5878
>                 URL: https://issues.apache.org/jira/browse/MESOS-5878
>             Project: Mesos
>          Issue Type: Bug
>          Components: tests
>            Reporter: Neil Conway
>            Assignee: Alexander Rukletsov
>              Labels: mesosphere
>         Attachments: strict_registrar_update_quota.log
>
>
> Observed on ASF CI 
> (https://builds.apache.org/job/Mesos/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-6)/2539/consoleFull).
>  Log file is attached. Note that this might have been uncovered due to the 
> recent removal of {{os::sleep}} from {{Clock::settle}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to