mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandra Sava" <>
Subject Re: Review Request 22754: First part of the deactivate slaves mechanism - HTTP deactivate endpoint
Date Tue, 01 Jul 2014 14:53:50 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated July 1, 2014, 2:53 p.m.)

Review request for mesos and Ben Mahler.

Repository: mesos-git

Description (updated)

This is the first part of the 'deactivate slave' mechanism.

This part consists of creating an HTTP endpoint which receives HTTP posts. Each post contains
a JSON object with a list of slave ids which operators want to deactivate. The list is further
passed to the master which marks them as 'deactivated' in the allocator. The final result
is that the master will no longer send resource offers belonging to the deactivates slaves.

The TODO for the second part is to make the list of deactivated slaves persistent, by storing
it into the Registry.

Diffs (updated)

  src/master/http.cpp 5d869767cd3ed48aae1e702e8d014a37ef371123 
  src/master/master.hpp 5fef35406c2ce2ad11e030aa7752eb691aab5857 
  src/master/master.cpp 474014b24982449f2f64c2e8d835c25a28cbcbb8 




Alexandra Sava

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