applied
On Mon, Jul 04, 2016 at 01:16:10PM +0200, Dominik Csapak wrote:
> when a load of an update store was ongoing and stopUpdate
> was called, the task could not be canceled, and the store
> would remain indefinitely
>
> this patch sets 'isStopped' of the store on stopUpdate
> and checks it on
What I am wondering is why do we treat the UpdateStore requests serially
in the first place ?
i think the intention was that if you have multiple updatestores, we do
not want to bombard the backend with api requests, but send them one
after another
___
On 07/04/2016 01:16 PM, Dominik Csapak wrote:
> when a load of an update store was ongoing and stopUpdate
> was called, the task could not be canceled, and the store
> would remain indefinitely
I can reproduce the problem you mention here ( when a node in a cluster
becomes unavailable in the netw
when a load of an update store was ongoing and stopUpdate
was called, the task could not be canceled, and the store
would remain indefinitely
this patch sets 'isStopped' of the store on stopUpdate
and checks it on the next update and stopping it then
Signed-off-by: Dominik Csapak
---
www/manage
