[jira] [Created] (MESOS-4831) Master sometimes sends two inverse offers after the agent goes into maintenance.

["Anand Mazumdar (JIRA)" <ji...@apache.org>]

Anand Mazumdar created MESOS-4831:
-------------------------------------

             Summary: Master sometimes sends two inverse offers after the agent goes into maintenance.
                 Key: MESOS-4831
                 URL: https://issues.apache.org/jira/browse/MESOS-4831
             Project: Mesos
          Issue Type: Bug
    Affects Versions: 0.27.0
            Reporter: Anand Mazumdar


Showed up on ASF CI for {{MasterMaintenanceTest.PendingUnavailabilityTest}}

{code}
I0229 11:08:57.027559   668 hierarchical.cpp:1437] No resources available to allocate!
I0229 11:08:57.027745   668 hierarchical.cpp:1150] Performed allocation for slave fd39ca89-d7fd-4df8-ad50-dbb493d1cd7b-S0 in 272747ns
I0229 11:08:57.027757   675 master.cpp:5369] Sending 1 offers to framework fd39ca89-d7fd-4df8-ad50-dbb493d1cd7b-0000 (default)
I0229 11:08:57.028586   675 master.cpp:5459] Sending 1 inverse offers to framework fd39ca89-d7fd-4df8-ad50-dbb493d1cd7b-0000 (default)
I0229 11:08:57.029039   675 master.cpp:5459] Sending 1 inverse offers to framework fd39ca89-d7fd-4df8-ad50-dbb493d1cd7b-0000 (default)
{code}

The ideal expected workflow for this test is something like:

- The framework receives offers from master.
- The framework updates its maintenance schedule.
- The current offer is rescinded.
- A new offer is received from the master with unavailability set.
- After the agent goes for maintenance, an inverse offer is sent.

For some reason, in the logs we see that the master is sending 2 inverse offers. The test seems to pass as we just check for the initial inverse offer being present. 

Also, unrelated, we need to clean up this test to not expect multiple offers i.e. remove {{numberOfOffers}} constant.



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