-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write note into log when automatic sweep is started [CORE2668] #3072
Comments
Commented by: Sean Leyne (seanleyne) Nice request! I would suggest one change. Log all sweep starts, not just those triggered by the sweep interval, but also those triggered via GFIX. It is possible for an admin to not know about a sweep which has been scheduled by another admin, or they could have forgotten themselves. |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: Christian Masberg (cubism) Very usefull! |
Commented by: Sean Leyne (seanleyne) One additional item, also log when the sweep ends/stops. |
Modified by: @dyemanovassignee: Alexander Peshkov [ alexpeshkoff ] => Vlad Khorsun [ hvlad ] Fix Version: 2.5.2 [ 10450 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Commented by: @hvlad firebird log will contain following records about sweep : a) when sweep started :
b) when sweep finished successfully (no errors was thrown) :
c) when some exception breaks the sweep execution : |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Submitted by: @aafemt
Relate to CORE3978
Votes: 9
It would be nice to have in log a record about automatic sweep start. This way DBA can notice problems (or no problems) with transaction management. Currently newbies blame sweep in all slowdowns and unnecessary tune autosweep interval.
Commits: 9124f5e 05dc7aa
The text was updated successfully, but these errors were encountered: