You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "José Guilherme Vanz (JIRA)" <ji...@apache.org> on 2015/09/01 04:08:45 UTC

[jira] [Comment Edited] (MESOS-1575) master sets failover timeout to 0 when framework requests a high value

    [ https://issues.apache.org/jira/browse/MESOS-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724582#comment-14724582 ] 

José Guilherme Vanz edited comment on MESOS-1575 at 9/1/15 2:08 AM:
--------------------------------------------------------------------

Well, I do not know [~gyliu]. As a novice in the project I am in doubt about what is the best approach. Maybe [~vinodkone] or [~kevints] have a better opinion.

I believe the idea of refuse the subscribe is notify the user that something can be wrong with his application instead of just silently use the default value. The default value can be used when the the parameter is missing... 

Anyway, I can update the default value. =)


was (Author: jvanz):
Well, I do not know [~gyliu]. As a novice in the project I am in doubt about what is the best approach. Maybe [~vinodkone] or [~kevints] have a better opinion.

Anyway, I can update the default value. =)

> 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
>            Assignee: José Guilherme Vanz
>              Labels: newbie, twitter
>
> 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.3.4#6332)