flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maximilian Michels <...@apache.org>
Subject Re: why job submit timeout is 21474835 second
Date Mon, 29 Aug 2016 16:56:14 GMT
This limitation doesn't exist anymore in the latest master. Jobs may
be monitored for infinite amount of time now. Note that it wouldn't
cancel the job if the submission timeout had been reached before the
job completed.

On Mon, Aug 29, 2016 at 6:06 PM, Till Rohrmann <trohrmann@apache.org> wrote:
> If I'm not mistaken then this was a limitation of Akka's ask futures. The
> maximum timeout was as specified. It might have changed with a new version,
> though. Usually, you should rarely run into a case where this actually
> matters.
>
> Cheers,
> Till
>
> On Mon, Aug 29, 2016 at 5:44 PM, Greg Hogan <code@greghogan.com> wrote:
>
>> Could be rewritten as "val INFO_TIMEOUT = Integer.MAX_VALUE seconds"?
>>
>> On Mon, Aug 29, 2016 at 4:22 AM, 时金魁 <shijinkui666@163.com> wrote:
>>
>> >
>> >
>> > AkkaUtils.scala
>> > val INF_TIMEOUT = 21474835 seconds
>> >
>> >
>> > That is job submit timeout 248.55 days.
>> >
>> >
>> > Why is this number?
>> >
>> >
>> >
>> >
>>

Mime
View raw message