Issue Details (XML | Word | Printable)

Key: CORE-2668
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Vlad Khorsun
Reporter: Dimitry Sibiryakov
Votes: 9
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Write note into log when automatic sweep is started

Created: 06/Oct/09 06:18 AM   Updated: 23/Apr/13 11:45 AM
Component/s: Engine
Affects Version/s: None
Fix Version/s: 2.5.2, 3.0 Alpha 1

Time Tracking:
Not Specified

Issue Links:
Relate
 

Target: 3.0.0
Planning Status: Unspecified


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Sean Leyne added a comment - 06/Oct/09 06:31 AM
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.

Christian Masberg added a comment - 01/Feb/10 05:20 PM
Very usefull!
Otherwise I don't know of a way of identifying the sweep interval, because it is not written into the server log.

Sean Leyne added a comment - 01/Feb/10 05:29 PM
One additional item, also log when the sweep ends/stops.

Vlad Khorsun added a comment - 28/Jun/12 10:05 AM - edited
firebird log will contain following records about sweep :

a) when sweep started :

     Sweep is started by <user name>
     Database <database name>
     OIT <n>, OAT <n>, OST <n>, Next <n>

b) when sweep finished successfully (no errors was thrown) :

     Sweep is finished
     Database <database name>
     OIT <n>, OAT <n>, OST <n>, Next <n>

c) when some exception breaks the sweep execution :
     Error during sweep:
     <error details>