MI mi
Misconfiguration Issue
Background background
MI (Misconfiguration Issue) Identifies configuration issues on AEM instance.
Subtypes are used to identify the different types of information, such as:
sling.job.max.parallel: Identify the sling jobs where max parallel configuration is set to -1.missing.maintenance.configuration: Identify missing Maintenance Task configurations.
Possible implications and risks implications-and-risks
sling.job.max.parallel- A value of -1 is substituted with the number of available processors. As such, it might cause performance issues on an AEM instance.
missing.maintenance.configuration- Missing Maintenance Task configurations may cause loss of performance or instance corruption.
Possible solutions solutions
-
sling.job.max.parallel- Adobe recommends setting the value to 0.5 to take advantage of half of the available processors.
-
missing.maintenance.configuration- Revision Clean Up: See Revision Clean Up. The important part regarding the configuration is here: Revision Cleanup - Configure Tail and Full compaction.
- Lucene Binaries Cleanup: See Operations Dashboard - Lucene Binaries Cleanup.
- Data Store Garbage Collection: See Data Store Garbage Collection.
- Workflow Purge: See Regular Purging of Workflow Instances.
- AuditLog Maintenance Task: See Audit Log Maintenance.
-
Contact the Experience Manager Customer Care Team for clarifications or to address concerns.
recommendation-more-help
experience-manager-pattern-detection-help-using