[MESOS-7661] Libprocess timers with long durations trigger immediately

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 1.5.0
• Component/s: libprocess
• Labels: mesosphere
• Sprint: Mesosphere Sprint 58, Mesosphere Sprint 59, Mesosphere Sprint 60, Mesosphere Sprint 61
• Story Points: 3
• Assignee: Gastón Kleiman
• Reporter: Gastón Kleiman
• Shepherd: Greg Mann
• Created: 13/Jun/17 23:46
• Updated: 14/Aug/17 21:20
• Resolved: 14/Aug/17 21:20

Description

process::delay() will schedule a method to be run right ahead when called with a veeeery long Duration.

This happens because Timeout tries to add two long durations, leading to an integer overflow in Duration.

I'd expect libprocess to either:

1. Never run the method.
2. Schedule it in the longest possible Duration.

Duration::operator+=() should probably also handle integer overflows differently. If an addition leads to an integer overflow, it might make more sense to return Duration::max() than a negative duration.

Issue Links

• blocks: MESOS-7514 ReservationTest.PreventUnreservingAlienResources is flaky