Kevin Sweeney created MESOS-1575:
------------------------------------
Summary: master sets failover timeout to 0 when framework requests
a high value
Key: MESOS-1575
URL: https://issues.apache.org/jira/browse/MESOS-1575
Project: Mesos
Issue Type: Bug
Reporter: Kevin Sweeney
In response to a registered RPC we observed the following behavior:
{noformat}
W0709 19:07:32.982997 11400 master.cpp:612] Using the default value for
'failover_timeout' becausethe input value is invalid: Argument out of the range
that a Duration can represent due to int64_t's size limit
I0709 19:07:32.983008 11404 hierarchical_allocator_process.hpp:408] Deactivated
framework 20140709-184342-119646400-5050-11380-0003
I0709 19:07:32.983013 11400 master.cpp:617] Giving framework
20140709-184342-119646400-5050-11380-0003 0ns to failover
I0709 19:07:32.983271 11404 master.cpp:2201] Framework failover timeout,
removing framework 20140709-184342-119646400-5050-11380-0003
I0709 19:07:32.983294 11404 master.cpp:2688] Removing framework
20140709-184342-119646400-5050-11380-0003
I0709 19:07:32.983678 11404 hierarchical_allocator_process.hpp:363] Removed
framework 20140709-184342-119646400-5050-11380-0003
{noformat}
This was using the following frameworkInfo.
{code}
FrameworkInfo frameworkInfo = FrameworkInfo.newBuilder()
.setUser("test")
.setName("jvm")
.setFailoverTimeout(Long.MAX_VALUE)
.build();
{code}
Instead of silently defaulting large values to 0 the master should refuse to
process the request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
