Short Description: Control whether or not DAOS resync may run at a given time
Another new feature added to 8.5.2 allows an administrator to control when DAOS resync will be allowed to run. While the impact of resync on a running server has been greatly reduced by improvements in 8.5.2, it still may not be desirable for resync to run during production hours. The following two notes.ini parameters control when resync will be allowed to run. Note that these parameters do not launch resync automatically; they just control whether or not resync may run at a given time, and also tell resync to stop at the stop time.
The format of the time is as follows: HH:MM:SS AM/PM
The above example will allow resync to run between midnight and 4:00 AM. A program document could be created to launch resync just after midnight. If the catalog is SYNCHRONIZED, then resync will not run. However, if a resync is needed, then resync will start the process above. When time reaches the end time, the resync threads will finish up the databases they are processing and exit. Because each thread will finish the NSF it is processing, the work may run slightly past the specified stop time. The next night, when resync is run again, it will pick up where it left off.
If resync finished processing all databases during the time window, then the catalog will go to the SYNCHRONIZED state. At this point there is still a little more work to be done to the catalog. Even though past the time window, this processing will be finished up. Therefore, there is a potential for resync to run past the end time, but the remaining work is low-impact and will not effect server response time.
Note that until resync scans all databases on the system and puts them into the SYNCHRONIZED state, the DAOS catalog will remain in the RESYNCING state. This indicates that resync still has work to be done. It does not, howeve,r indicate that resync is currently running.
Overview of 8.5.2 Improvements in DAOS Catalog