I have a timer job that invokes a WCF service that invokes a single threaded API internally.
TO ensure that my system does not fail, i want to ensure that only a single instance runs at a time.
I am setting SPJobLockType.Job t ensure this.
My concern is, what happens when the timer job schedule is too frequent? What happens when an old instance of the timer job is still running when the new instance is scheduled to run?
Will the new instance of the timer job just defer its execution? or does it abort itself? Or does it abort the old version?
In general, what are the best practices to ensure that my above described scenario runs without any failures?