[PATCH] restructure messaging

[Volker Lendecke]

Andrew Bartlett <abartlet at samba.org> writes:

> On Mon, 2016-10-03 at 19:53 +0200, Volker Lendecke wrote:
> Great, that should be enough.  Does that include in the single-process
> case?  

Yes.

> Yes and No.  Currently our code can get stuck for that long and longer
> blocked with the transaction lock held in the client-side of
> replication.  That is a serious issue we are working on, as you can
> imagine it creates pretty serious issues. 

What semantics does the AD controller need for messaging? Queue
indefinitely? Set the timeout to an hour or a day? I feel a bit uneasy
queuing things forever, maybe a one-day timeout is appropriate for the
AD DC? What happens if it blocks for full 24 hours? Do the clients work
fine with that?

> Bugs aside, the main use case we have that can wait for minutes or
> hours is waiting for replication to complete, but that isn't meant to
> be blocking, but a very long time before the reply, and I think that is
> quite different.

Do you expect 24 hours to be a reasonable timeout for replication to
complete? I want *SOME* timeout, I don't want things to pile up
indefinitely.

Regards,

Volker