Mercury Release 4

Mercury Release 4

We are pleased to announce the availability of Mercury Release 4. Mercury 4.0 introduced a new ActionManager, which is the part of Mercury that does things to products after the FileDetector detects them:

  • The ActionManager’s “state” is managed differently. Prior to 4.0, state was only saved when a Remote Agent shut down nicely. Since a nice shutdown can take several seconds (giving child processing a chance to stop cleanly), in real life the Remote Agent is often shut down quickly, which meant that Mercury 3’s ActionManager state often was lost. Mercury 4’s ActionManager saves state as it changes to minimize losses when the Remote Agent is shut down quickly.
  • Mercury 4 adds the notion of “resource”, which is a generalization of the way Mercury 3 could restrict the number of simultaneous product pushes. Resources can be used, for example, to restrict the number of products that can be processed simultaneously: Imagine a long-running and computationally expensive processing step, and hundreds of products arriving all at once.
  • Mercury 4 allows more powerful control of which steps can be executed in parallel vs in sequence.
  • Mercury 4.0 also provides a foundation which will enable better awareness and control over the ActionManager in future releases.

The current release of Mercury is 4.1, which provides bug fixes and minor enhancements over 4.0.