Release Notes
Product Version Information
NOTE
MindCluster 26.0 version planning: MindCluster 26.0.0, MindCluster 26.1.0, MindCluster 26.2.0, and MindCluster 26.3.0.
Product Version Mapping
| Product Name | Version |
|---|---|
| Ascend HDK |
|
| CANN | 9.0.0 |
Virus Scan Results
Virus scan passed.
MindCluster components must be used together. Do not mix components from different versions.
Table 1 Software version compatibility description
| MindCluster Software Version | MindCluster Version to Upgrade | CANN Version | Ascend HDK Version | FrameworkPTAdapter Version | MindSpore Version |
|---|---|---|---|---|---|
| MindCluster 26.0.0 |
|
|
|
|
|
None
New Features
| Feature | Description |
|---|---|
| MindIO ACP | Supports Async CheckPoint Persistence (ACP) and Training Fault Tolerance (TFT). |
| MindIO TFT |
|
| MindCluster Ascend FaultDiag |
|
| MindCluster basic components |
|
Key Feature Changes
MindCluster basic components:
- The gRPC heartbeat detection interval of ClusterD is adjusted from the default 5 minutes to 5 seconds.
- The automatic forced isolation and release of repeatedly faulty chips at the cluster dimension is supported.
- For the Atlas 350 PCIe card:
- The task resource request
huawei.com/Ascend910is changed tohuawei.com/npu. - The underlying DCMI is changed to the DCMI V2.
- The task resource request
Service Interface Changes
| Feature | Interface Change |
|---|---|
| MindIO ACP | None |
| MindIO TFT | New tft_register_exception_handler interface that registers an exception handler. |
| MindCluster Ascend FaultDiag | New interfaces related to Ascend-faultdiag-toolkit. For details, see API Description. |
| MindCluster basic components |
|
Resolved Issues
- When resources such as MindIO processor are released and the program crashes, TaskD Agent cannot exit. A fallback exit mechanism is added.
- After training ends, when TaskD Worker calls the
mspti_activity_flush_allmethod, adouble freeerror is reported. - Concurrent map read/write by TaskD Manager causes process crash.
- Delayed update of pg cache in ClusterD.
- Forced requirement for healthy RoCE network between MindIE instances causes MindIE task scheduling failure.
- Pod does not exit after training completion in the user-defined torch log file scenario.
- When NodeD is installed and the cluster has more than 1024 cards, the gRPC connection limit of ClusterD is exceeded, preventing other connections from being established
Known Issues
None
Impact of the Upgrade Process on the Current System
None
Impact on the Current System After Upgrade
None
| Document | Content Description | Release Notes |
|---|---|---|
| MindCluster Cluster Scheduling User Guide | Introduces cluster scheduling components, feature principles, and usage references, including installation and deployment, integration and adaptation examples, and API references for each component, as well as working principles for some scheduling solutions. | Adds soft partitioning-based scheduling and multi-level scheduling. |
| MindCluster Fault Diagnosis User Guide | Provides usage guidance for features such as log collection, cleaning and dumping, and troubleshooting. | Adds the Atlas 350 PCIe card fault mode and ascend-faultdiag-toolkit. |
None