Bug 49442 – Reduce S4-Connector latency - let it wake up when UCS changes are incoming

Bug 49442 - Reduce S4-Connector latency - let it wake up when UCS changes are incoming


Summary:	Reduce S4-Connector latency - let it wake up when UCS changes are incoming

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:	49415
	Show dependency tree / graph

Reported:	2019-05-09 21:29 CEST by Arvid Requate
Modified:	2021-02-10 20:44 CET (History)
CC List:	3 users (show)

See Also:	49415 52358
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	UCS Performance
Max CVSS v3 score:

Attachments
0001-Make-S4-Connector-wake-up-when-changes-are-incoming-.patch (2.20 KB, patch) 2019-05-09 21:29 CEST, Arvid Requate	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2019-05-09 21:29:09 CEST

Created attachment 10018 [details]
0001-Make-S4-Connector-wake-up-when-changes-are-incoming-.patch

For Bug #49415 we need to get more control over the replication timing of the S4-Connector. In out CI tests we have to wait a lot for S4-Connector activity to settle. To reduce this time, we could reduce the poll/sleep phases and make the S4-Connector wake up as soon as a new pickle file is moved to /var/lib/univention-connector/s4 .

See attached patch for a simple, effective proposal.

Comment 1 Florian Best

2020-11-13 19:46:09 CET

I really would like to see this change in the product.
Before applying it we should carefully check, which errors could happen by using inotify.
I remember that we had customer systems in the past, which had limits about max open file descriptors, which stopped inotify to work (See Bug #32327, Bug #31752, (Bug #24165, Bug #26277)).

Comment 2 Florian Best

2021-02-10 20:44:48 CET

Patch also in git branch arequate/49442-s4c-sleep-with-inotify.