We would like to implement a customized backup policy for GigaSpaces log files, in order to automatically gzip rolled files. According to the documentation, we must implement interface com.gigaspaces.logger.BackupPolicy and provide it to GigaSpaces components when they are started.
Once we have a JAR with an implementation of the customized backup policy, what are the best practices for providing classes to GigaSpaces runtime? Should we just put the JAR into "$GS_HOME/lib/required", or are there another recommendations?
Another related question: is the callback method in the interface BackupPolicy invoked in a separate thread /pool, or is it invoked from a thread which has a lot of other tasks? Or, to put it differently: is it a good idea to run a long-running task, such as zipping a large file, directly in the callback method, or is it recommended to execute long-running tasks in a separate thread?
And one more question: is it guaranteed that the callback method in the interface BackupPolicy is always invoked from the same thread? Based on the answer, an internal synchronization may be required in the implementation of the BackupPolicy.
↧