
|
If you were logged in you would be able to see more operations.
|
|
|
Bruce
Created: 06/Nov/07 02:08 PM
Updated: 06/Nov/07 02:09 PM
|
|
| Component/s: |
Daemon
|
| Affects Version/s: |
1.0
|
| Fix Version/s: |
1.5
|
|
Problem: When the master database is down, and a log switch is attempted, the LogSwitch thread terminates, and logs are no longer switched.
Workaround #1: While the database remains up, bring down the daemon, and start it with a value of the bruce.retainTime property set greater than the time the most recent log was created. The value of bruce.retainTime is in minutes, i.e. a value of 20160 means 14 days (14days*24hours*60minutes=20160minutes). Once each slave has moved beyond the transactions captured in the ex-most recent log (when the daemon is restarted, a new transaction/snapshot log should be created), it is safe to restart the daemon with its default value of 5 days (7200 minutes)
Workaround #2: Restart the daemon soon after the master database is restarted.
|
|
Description
|
Problem: When the master database is down, and a log switch is attempted, the LogSwitch thread terminates, and logs are no longer switched.
Workaround #1: While the database remains up, bring down the daemon, and start it with a value of the bruce.retainTime property set greater than the time the most recent log was created. The value of bruce.retainTime is in minutes, i.e. a value of 20160 means 14 days (14days*24hours*60minutes=20160minutes). Once each slave has moved beyond the transactions captured in the ex-most recent log (when the daemon is restarted, a new transaction/snapshot log should be created), it is safe to restart the daemon with its default value of 5 days (7200 minutes)
Workaround #2: Restart the daemon soon after the master database is restarted.
|
Show » |
| There are no comments yet on this issue.
|
|