Re: updateconfig doc

2017-10-30 Thread 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

Re: updateconfig doc

2017-10-30 Thread Mohit Jaggi
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

Re: updateconfig doc

2017-10-30 Thread Bill Farner
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 >

Re: updateconfig doc

2017-10-30 Thread Bill Farner
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

Re: updateconfig doc

2017-10-30 Thread Joshua Cohen
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