mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mesos Reviewbot Windows <revi...@mesos.apache.org>
Subject Re: Review Request 69980: Modified when master responds to operation status updates.
Date Wed, 20 Feb 2019 01:54:37 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69980/#review212936
-----------------------------------------------------------



FAIL: Some of the unit tests failed. Please check the relevant logs.

Reviews applied: `['69960', '69961', '69962', '69963', '69967', '69980']`

Failed command: `Start-MesosCITesting`

All the build artifacts available at: http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2902/mesos-review-69980

Relevant logs:

- [mesos-tests.log](http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2902/mesos-review-69980/logs/mesos-tests.log):

```
I0220 01:54:20.080921 60676 ex832fb4-0000 because it is terminating
I0220 01:54:20.081923 56988 master.cpp:1269] Agent ae10102e-10e4-48ec-a6f2-9674e6832fb4-S0
at slave(491)@192.10.1.6:56719 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
disconnected
I0220 01:54:20.082947 56988 master.cpp:3292] Disconnecting agent ae10102e-10e4-48ec-a6f2-9674e6832fb4-S0
at slave(491)@192.10.1.6:56719 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0220 01:54:20.082947 56988 master.cpp:3311] Deactivating agent ae10102e-10e4-48ec-a6f2-9674e6832fb4-S0
at slave(491)@192.10.1.6:56719 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0220 01:54:20.082947 60756 hierarchical.cpp:390] Removed framework ae10102e-10e4-48ec-a6f2-9674e6832fb4-0000
I0220 01:54:20.082947 60756 hierarchical.cpp:827] Agent ae10102e-10e4-48ec-a6f2-9674e6832fb4-S0
deactivated
I0220 01:54:20.084924 56988 containerizer.cpp:2526] Destroying container 8c59f777-acc4-44f0-9a79-9f3c92f58614
in RUNNING state
I0220 01:54:20.084924 56988 containerize[       OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0
(685 ms)
[----------] 1 test from IsolationFlag/MemoryIsolatorTest (704 ms total)

[----------] Global test environment tear-down
[==========] 1112 tests from 105 test cases ran. (557867 ms total)
[  PASSED  ] 1111 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] DockerFetcherPluginTest.INTERNET_CURL_FetchImage

 1 FAILED TEST
  YOU HAVE 232 DISABLED TESTS

r.cpp:3193] Transitioning the state of container 8c59f777-acc4-44f0-9a79-9f3c92f58614 from
RUNNING to DESTROYING
I0220 01:54:20.084924 56988 launcher.cpp:161] Asked to destroy container 8c59f777-acc4-44f0-9a79-9f3c92f58614
W0220 01:54:20.085935 61824 process.cpp:1423] Failed to recv on socket WindowsFD::Type::SOCKET=5756
to peer '192.10.1.6:58703': IO failed with error code: The specified network name is no longer
available.

W0220 01:54:20.086922 61824 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=5720
to peer '192.10.1.6:58704': IO failed with error code: The specified network name is no longer
available.

I0220 01:54:20.105926 56988 containerizer.cpp:3032] Container 8c59f777-acc4-44f0-9a79-9f3c92f58614
has exited
I0220 01:54:20.133921 53304 master.cpp:1109] Master terminating
I0220 01:54:20.135931 59500 hierarchical.cpp:678] Removed agent ae10102e-10e4-48ec-a6f2-9674e6832fb4-S0
I0220 01:54:20.938930 61824 process.cpp:927] Stopped the socket accept loop
```

- Mesos Reviewbot Windows


On Feb. 19, 2019, 4:47 p.m., Joseph Wu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69980/
> -----------------------------------------------------------
> 
> (Updated Feb. 19, 2019, 4:47 p.m.)
> 
> 
> Review request for mesos, Benno Evers, Gastón Kleiman, and Greg Mann.
> 
> 
> Bugs: MESOS-9542
>     https://issues.apache.org/jira/browse/MESOS-9542
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> When dealing with orphaned operation status updates, there are two
> cases the master must deal with:
> - The simple case is when the master knows the framework is completed.
>   These status updates can be acknowledged by the master.
> - However, a completed framework can be rotated out of the master's
>   memory.  In addition, after master failover, if an agent reregisters
>   before the framework, an operation can appear to be orphaned until
>   the framework reregisters.
> 
> This adds a fixed delay between agent reregistration and when the
> master acknowledges operation status updates from unknown frameworks.
> The delay should give frameworks ample time to reregister.
> 
> The delay is based on agent reregistration in order to mitigate the
> delay of acknowledging status updates of frameworks rotated out of
> the completed frameworks buffer.
> 
> 
> Diffs
> -----
> 
>   src/master/constants.hpp b0ab9187b8c672180e2ffb8b63cb7349dbe43ac4 
>   src/master/master.cpp 106d924bf16231b3bda3fb719db68c01d73644ee 
> 
> 
> Diff: https://reviews.apache.org/r/69980/diff/2/
> 
> 
> Testing
> -------
> 
> TODO: This case needs unit tests.
> 
> 
> Thanks,
> 
> Joseph Wu
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message