[DCMEE-1936] scheduler does not run for ScheduleStudiesForDeletion after failover to new master node Created: 18/Feb/13 Updated: 28/Nov/18 Resolved: 28/Nov/18 |
|
| Status: | Closed |
| Project: | dcm4chee |
| Components: | Deleter |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Christopher Archer | Assignee: | Gunter Zeilinger |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Testing Assignee: | Peter Heiles |
| Tracking Status: |
Risk Analysis - Todo, Test Spec - ToReview, Test State - Not tested
|
| Sprint: |
| Description |
|
When the current master node had to be restarted, deletes were no longer seen from the new master node. The log in INFO mode would not show any indicators that ScheduleStudiesForDeletion was being periodically run. The symptom is a steady decline in free online cache and the related log messages showing only the (declining) free space on the current online cache volume. |
| Comments |
| Comment by Christopher Archer [ 18/Feb/13 ] |
|
Suggested change: dcm4jboss-sar/src/java/org/dcm4chex/archive/mbean/FileSystemMgt2Service.java, method stopService super.stopService(); |