Object retrieval delay considerations and examples - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

You should use care when choosing the object retrieval delay. A long delay may impact the ability of system journal replication processes to move data from a system in a timely manner. Too short a delay may allow MIMIX to retrieve an object before an application is finished with it. You should make the value large enough to reduce or eliminate contention between MIMIX and applications, but small enough to allow MIMIX to maintain a suitable high availability environment.

Example 1 - The object retrieval delay value is configured to be 3 seconds:

  • Object A is created or changed at 9:05:10.

  • The Object Retrieve job encounters the create/change journal entry at 9:05:14. It retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 9:05:10 + configured delay value of :03 = 9:05:13) is less than the current date/time (9:05:14). Because the object retrieval delay time has already been exceeded, the object retrieve job continues normal processing and attempts to package the object.

Example 2 - The object retrieval delay value is configured to be 2 seconds:

  • Object A is created or changed at 10:45:51.

  • The Object Retrieve job encounters the create/change journal entry at 10:45:52. It retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 10:45:51 + configured delay value of :02 = 10:45:53) exceeds the current date/time (10:45:52). Because the object retrieval delay value has not be met or exceeded, the object retrieve job delays for 1 second to satisfy the configured delay value.

  • After the delay (at time 10:45:53), the Object Retrieve job again retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 10:45:51 + configured delay value of :02 = 10:45:53) is equal to the current date/time (10:45:53). Because the object retrieval delay value has been met, the object retrieve job continues with normal processing and attempts to package the object.

Example 3 - The object retrieval delay value is configured to be 4 seconds:

  • Object A is created or changed at 13:20:26.

  • The Object Retrieve job encounters the create/change journal entry at 13:20:27. It retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 13:20:26 + configured delay value of :04 = 13:20:30) exceeds the current date/time (13:20:27) and delays for 3 seconds to satisfy the configured delay value.

  • While the object retrieve job is waiting to satisfy the configured delay value, the object is changed again at 13:20:28.

  • After the delay (at time 13:20:30), the Object Retrieve job again retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 13:20:28 + configured delay value of :04 = 13:20:32) again exceeds the current date/time (13:20:30) and delays for 2 seconds to satisfy the configured delay value.

  • After the delay (at time 13:20:32), the Object Retrieve job again retrieves the “last change date/time” attribute from the object and determines that the delay time (object last changed date/time of 13:20:28 + configured delay value of :04 = 13:20:32) is equal to the current date/time (13:20:32). Because the object retrieval delay value has now been met, the object retrieve job continues with normal processing and attempts to package the object.