Latest Release
A brief introduction to MMBatch followed by what's new in the latest release.
Overview
Memory Machine Batch (MMBatch) captures the entire running state of a Batch Job into a consistent image and restores the Job on a new Compute Instance without losing any work progress. It ensures a high quality of service at the Batch level using low-cost, but unreliable Spot-based Compute Instances. For more details, visit the MMBatch website.
New in the 1.2 Release
The MMBatch 1.2 release adds new features, improves the user experience and enhance security of the product.
-
Workflow Manager Support
-
MMBatch Management Server
-
AWS Cognito Support
- User can utilize existing AWS Cognito credentials to sign in MMBatch’s Management Server starting in 1.2.
- For how to enable/disable Cognito as well as signing in, see here.
-
Security
- MMBatch supports both IMDSv1 and IMDSv2 starting in 1.2.
-
RESTFUL API
- MMBatch provides RESTFUL APIs starting in 1.2.
- For the API reference guide, see here.
Known Limitations
- When an AWS Spot Interruption event triggers, the AWS instance is terminated after 2 minutes. Depending on checkpoint volume storage configuration, around 30GB of data can be saved during this period. The data is the total of memory usage plus container filesystem usage. The actual amount of data saved depends on multiple factors including storage type, storage bandwidth, the number of jobs running on the AWS instance being reclaimed. It is recommended to attach a shared filesystem for container scratch files instead of writing to the container filesystem. An attached shared filesystem data does not require saving during checkpoint. The recommended shared filesystem is JuiceFS with S3 backing.
- When signing up AWS Cognito service from MMBatch Management Server, with username alone, both email address and phone number are required attributes.