Flume Agent Unexpectedly Exits
Last updated on MAY 31, 2016
Applies to:Big Data Appliance Integrated Software - Version 4.4.0 and later
With three flume agents running, suddenly, one agent starts to give three bad health codes, Unexpected Exits, Process Status, and Web Server Status.
When this happens, the CPU for the bad agent stays really high, around 60%. Prior to the sudden bad health codes, the three agents were running fine.
Rebalancing the agent does not help. It fixes the issue for a short period of time, then the bad health codes return.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms