URL:
https://github.com/SSSD/sssd/pull/5552
Title: #5552: files: split update into batches
sumit-bose commented:
"""
The reason why the message is not delivered is because we send it
over `provider->sbus_conn` which requires accessing the backend's tevent loop
because the backend runs this message bus. If `be_ctx->mon_conn` is used instead the
message is sent through the monitor's message bus immediately.
Hi @pbrezina,
this sounds like the proper solution for #5091. There were discussions about dropping the
monitor and relying on systemd to start the SSSD components. I do not remember the current
state of those discussions but if we ever want to move that way this would be another task
of the monitor which must be replaced.
About @elkoniu's suggestion to wait with the processing of the files until the
messages are send. This can be easily combined with @alexey-tikhonov 's original
understanding of batches where we should not immediately start processing if we are
notified of a change but wait for e.g. 1s of inactivity on the files and start processing.
With this we should be long enough in the event loop to properly finish the communication
with the NSS responder, but I guess you would still recommend to send the message via the
monitor?
bye,
Sumit
"""
See the full comment at
https://github.com/SSSD/sssd/pull/5552#issuecomment-814828582