Hi Ken,
Awesome! IMO it works for us.
Thanks
Renat Akhmerov
@Nokia
On 20 Oct 2018, 01:19 +0700, Ken Giusti , wrote:
> Hi Renat,
> After discussing this a bit with Ben on IRC we're going to push the removal
> off to T milestone 1.
>
> I really like Ben's idea re: adding a blocking entry to your
Hi Renat,
After discussing this a bit with Ben on IRC we're going to push the removal
off to T milestone 1.
I really like Ben's idea re: adding a blocking entry to your project's
setup.cfg file. We can remove the explicit check for blocking in
oslo.messaging so you won't get an annoying warning
Hi,
@Ken, I understand your considerations. I get that. I’m only asking not to
remove it *for now*. And yes, if you think it should be discouraged from using
it’s totally fine. But practically, it’s been the only reliable option for
Mistral so far that may be our fault, I have to admit,
On 10/18/18 9:59 AM, Ken Giusti wrote:
Hi Renat,
The biggest issue with the blocking executor (IMHO) is that it blocks
the protocol I/O while RPC processing is in progress. This increases
the likelihood that protocol processing will not get done in a timely
manner and things start to
Hi Renat,
The biggest issue with the blocking executor (IMHO) is that it blocks the
protocol I/O while RPC processing is in progress. This increases the
likelihood that protocol processing will not get done in a timely manner
and things start to fail in weird ways. These failures are timing
