[MESOS-4111] Provide a means for libprocess users to exit while ensuring messages are flushed.

• Type: Bug
• Status: Accepted
• Priority: Minor
• Resolution: Unresolved
• Component/s: libprocess
• Assignee: Unassigned
• Reporter: Benjamin Mahler
• Created: 10/Dec/15 02:39
• Updated: 20/Jan/16 02:32

Description

Currently after a send there is no way to ensure that the message is flushed on the socket before terminating. We work around this by inserting os::sleep calls (see MESOS-243, MESOS-4106).

There are a number of approaches to this:

(1) Return a Future from send that notifies when the message is flushed from the system.

(2) Call process::finalize before exiting. This would require that process::finalize flushes all of the outstanding data on any active sockets, which may block.

Regardless of the approach, there needs to be a timer if we want to guarantee termination.

Issue Links

• is related to: MESOS-4106 The health checker may fail to inform the executor to kill an unhealthy task after max_consecutive_failures.
• is related to: MESOS-243 driver stop() should block until outstanding requests have been persisted