Skip to content
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

Closed
firebird-automations opened this issue Oct 6, 2009 · 12 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

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.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Open [ 1 ]

Target: 3.0.0 [ 10048 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Christian Masberg (cubism)

Very usefull!
Otherwise I don't know of a way of identifying the sweep interval, because it is not written into the server log.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

One additional item, also log when the sweep ends/stops.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ] => Vlad Khorsun [ hvlad ]

Fix Version: 2.5.2 [ 10450 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

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>

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue relate to CORE3978 [ CORE3978 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Done successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants