AEM Author logs show transient INFO-level MongoDB connection errors during managed node changes
AEM Author logs can show transient INFO-level MongoDB connection exceptions during Adobe-managed MongoDB scaling, rolling restarts, DNS changes, or primary elections. These entries occur when DocumentNodeStore briefly tries to connect to a node that is restarting, entering quiesce mode, or no longer available, and the connection is retried automatically. If the messages remain at INFO level and authoring continues to work normally, they do not indicate data loss or a service outage. Check the log level, verify whether authoring is affected, and contact Adobe Support only if the errors continue or affect normal use.
Description description
Environment:
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- AEM Managed Services
- Adobe Experience Manager Sandbox
Issue/Symptoms:
- AEM Author logs contain INFO-level MongoDB exceptions such as
MongoNodeIsRecoveringException,MongoSocketOpenException,MongoSocketException, orMongoCommandException. - Log entries include messages such as
ShutdownInProgress,Exception opening socket,No address associated with hostname, orKeyNotFound. - The
DocumentNodeStorebackground read thread invalidates cache after a transient MongoDB connection exception and continues running. - These messages appear during routine MongoDB operations such as scaling, rolling restarts, DNS transitions, or primary elections.
- These entries do not indicate a real outage unless they occur with sustained author unavailability, slowness, or repository issues.
Cause:
Adobe-managed MongoDB clusters rotate nodes during autoscaling, rolling restarts, DNS transitions, and primary elections. When a node enters quiesce mode or is removed from DNS, AEM Author can briefly try to connect to a node that is no longer available. This produces transient exceptions that are logged at INFO level and retried automatically by DocumentNodeStore. These messages do not indicate data loss or performance issues unless authoring is also affected.
Resolution resolution
To resolve this issue, follow the steps below:
- Open the Author
error.login Cloud Manager and verify that the MongoDB exceptions are logged at INFO level. - Check that authoring is working normally by opening pages and performing the affected action.
- Compare the log entries to expected transient patterns such as
ShutdownInProgress,Exception opening socket,No address associated with hostname, orKeyNotFound. - Review whether the entries appear in short bursts around recent scaling activity, high traffic, or deployments, and verify that they stop on their own.
- If the entries remain at INFO level and authoring is unaffected, no further action is required.
- Contact Adobe Support if the entries appear as WARN or ERROR, continue for more than 15 minutes, or occur with page load failures, slow authoring, or other functional impact.