Release notes

New Features, Improvements and Enhancements

Cross-Instance Processing Result Reuse by File Hash

MD Cluster 2.6.1 supports cross-instance processing result reuse by file hash. When the same file is submitted, an MD Core instance can reuse existing processing results instead of processing the file again. If the original file is still being processed, the requesting instance waits for completion before reusing the result. This helps reduce bandwidth usage and improves resource efficiency, especially for complex tasks.

Remote Upgrade Support for MD Cluster Worker

MD Cluster 2.6.1 now supports remote upgrades for MD Cluster Workers directly from Control Center. System administrators can trigger upgrades centrally, and all connected MD Cluster Workers will be upgraded automatically without requiring manual intervention.

RESTful API

• Added blocklisted_reason and allowlisted_reason fields to the response of GET /file/{data_id}, GET /file/batch/{batch_id} and GET /hash/{md5|sha1|sha256|sha512}.
• Added support for the GET /file/{data-id}/extraction-errors API endpoint.

Further Enhancements

1. Search Executive Reports by Workflow Rule Name

MD Cluster 2.6.1 allows users to filter executive reports by workflow rule name.

2. Separate Protected File Verdicts

Added separate verdicts for password-protected and RMS-protected document files.

3. Two-Year Executive Report Access

Users can now view executive reports for data spanning up to 2 years.

4. Archive Nesting Visibility

Archive scan results now include archive nesting levels for better visibility into nested files.

5. Extraction Issue Reporting

Extraction issues from all archive levels are now collected and displayed to help users identify problems during extraction.

Security Enhancements

• Upgraded NGINX to v1.30.1.
• Upgraded PostgreSQL to v14.23.
• Access to available rules, password policy settings, and active performance reports in MD Cluster Control Center can now be restricted based on user permissions.

Bug Fixes

• Fixed an issue where MD Core support packages larger than 4 GB could not be generated.
• Fixed an issue that prevented an engine from being disabled on MD Cluster Control Center while it was waiting for installation in MD Core instance.
• Fixed an issue where passwords were not retained in files generated through distributed compression.

Known Limitations

• MD Cluster Control Center does not detect duplicate workers when one is added using its IP address and another using its hostname (or vice versa). Registering the same worker multiple times may lead to incorrect license usage calculations.