OSA Pipeline Failed To Publish And Container Logs Help Required (Doc ID 2933021.1)

Last updated on JUNE 04, 2024

Applies to:

Oracle Stream Analytics - Version 19.1.0.0.1 and later
Information in this document applies to any platform.

Goal

It is observed that one of the existing pipeline was getting into Failed state in Yarn manager when we were trying to published and process the data flow with following message " Maximum number of executor reached" in OSA UI. To debug further we were unable to get the yarn logs for the application id in terminal and yarn console. We need help in checking the log aggregator configuration for the OSA configuration to fix the container logs issue.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

OSA Pipeline Failed To Publish And Container Logs Help Required (Doc ID 2933021.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!