This problem reminds me of a patch I have added for the observer to commit
suicide on unhandled errors in threads. See
https://github.com/apache/aurora/commit/d56f8c64466a94a990db3308a3130d3fce0584af
I will prepare a similar patch for the executor.
From: Bill Farner
Correct!
On Mon, Oct 30, 2017 at 2:32 PM, Mohit Jaggi wrote:
> Got it...and wait_for_batch_completion changes this from a "sliding" to a
> "rolling" window ?
>
> On Mon, Oct 30, 2017 at 2:28 PM, Bill Farner wrote:
>
>> Joshua beat me to the reply, so
Folks,
Does the following doc mean A or B?
*A*: batch_size is the number of instances in a given shard
*B:* batch_size is the number of shards. So every batch has (number of
instances)/(batch_size) tasks.
Mohit.
UpdateConfig Objects
Parameters for controlling the rate and policy of rolling
It's C: batch_size is the number of instances that can be updated at a
given time.
There's no direct relation between batch size and total number of
shards/instances. E.g. for a job with 100 instances and a batch size of 10,
at most 10 instances will be updating at a given time. If it turns out
Clarification - shard and instance are (unfortunately) used interchangeably
in some of our docs, despite the fact that shard can have a different
meaning in other contexts.
The meaning of batch_size doesn't match either rephrasing you offer,
perhaps the docs need work! batch_size effectively
Got it...and wait_for_batch_completion changes this from a "sliding" to a
"rolling" window ?
On Mon, Oct 30, 2017 at 2:28 PM, Bill Farner wrote:
> Joshua beat me to the reply, so now you have corroboration for his
> correction :-)
>
> On Mon, Oct 30, 2017 at 2:26 PM, Bill
Joshua beat me to the reply, so now you have corroboration for his
correction :-)
On Mon, Oct 30, 2017 at 2:26 PM, Bill Farner wrote:
> Clarification - shard and instance are (unfortunately) used
> interchangeably in some of our docs, despite the fact that shard can have a
>
great. would be awesome if this can be included in 0.18.1.
On Mon, Oct 30, 2017 at 3:18 PM, Erb, Stephan
wrote:
> This problem reminds me of a patch I have added for the observer to commit
> suicide on unhandled errors in threads. See https://github.com/apache/
>