You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2016/03/04 01:54:40 UTC
[jira] [Created] (MESOS-4862) Setting failover_timeout in
FrameworkInfo to Double.MAX_VALUE causes it to be set to zero
Timothy Chen created MESOS-4862:
-----------------------------------
Summary: Setting failover_timeout in FrameworkInfo to Double.MAX_VALUE causes it to be set to zero
Key: MESOS-4862
URL: https://issues.apache.org/jira/browse/MESOS-4862
Project: Mesos
Issue Type: Bug
Components: master, stout
Reporter: Timothy Chen
Currently we expose framework failover_timeout as a double in Proto, and if users set the failover_timeout to Double.MAX_VALUE, the Master will actually set it to zero which is the complete opposite of the original intent.
The problem is that in stout/duration.hpp we only store down to the nanoseconds with int64_t, and it gives an error when we pass double.max as it goes out of the int64_t bounds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)