-
Notifications
You must be signed in to change notification settings - Fork 1
Known issues
Oriol edited this page May 28, 2025
·
2 revisions
The execution of Python+MPI+EAR is not 100% automatic. Given Python is not a compiled language, the EAR loader cannot detect the MPI version automatically. Check in the User guide how to deal with this use case.
The EAR Loader has several methods for detecting the application use case to select the correct EAR Library to load.
When it tests whether the application is MPI, if it finds libmpi.so symbols it will load an MPI version of the EAR Library.
Therefore, the Library init method is called just after MPI_Init call function of the application, so, if your application is not calling this method, the EAR Library will not be started, and no metrics will be reported.
- Home
- User guide
- Tutorials
- Commands
- Environment variables
- Admin Guide
- Installation from source
- Architecture/Services
- High Availability support
- Configuration
- Classification strategies
- Learning phase
- Plug-ins
- Powercap
- Report plug-ins
- Database
- Supported systems
- EAR Data Center Monitoring
- CHANGELOG
- FAQs
- Known issues