Learn more about these different git repos.
Other Git URLs
This ticket is forked out of #1823.
In some environments, requesting a huge group might result in a request, that is running for so long in the background that the background is not responding to pings and gets killed by the monitor. This can be dangerous especially in situation where the back end was just in the middle of an ldb transaction.
We should think about a way to make SSSD respond to pings if it is legitimately processing a long-running request.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => 0 type: defect => task
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1022242 (Red Hat Enterprise Linux 6)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1022242 1022242]
cc: => jwm@horde.net changelog: => review: => 0
mark: => 0
We'll provide the background refresh in 1.13 alpha instead.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: major => minor
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @pbrezina: - Custom field design_review adjusted to on (was: 0) - Custom field mark adjusted to on (was: 0) - Custom field patch adjusted to on (was: 0) - Custom field review adjusted to on (was: 0) - Custom field sensitive adjusted to on - Custom field testsupdated adjusted to on (was: 0) - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Watchdog fixed this.
Actually Alexey pointed out that watchdog still depends on hitting a tevent loop so this ticket is still valid.
Metadata Update from @pbrezina: - Issue status updated to: Open (was: Closed)
Metadata Update from @pbrezina: - Issue tagged with: Future milestone
I do not think so. Stuck tevent loop will trigger watchdog and process will be restarted. So it just changed who restarts process (monitor -> internal watchdog) but problem remains - long running task will trigger process restart.
Afair there were some things done to process big batches in parts, but I don't remember exactly where did it apply...
Metadata Update from @atikhonov: - Issue untagged with: Future milestone
Metadata Update from @atikhonov: - Custom field feature_milestone adjusted to Future milestone
Metadata Update from @atikhonov: - Issue tagged with: Future milestone
#3271 was closed as duplicate of this ticket
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2871
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.