Flume Service Level Configuration File Changes are Not being Propagated to the Agents
Last updated on OCTOBER 11, 2016
Applies to:Big Data Appliance Integrated Software - Version 3.0.1 and later
Flume Service with one or more agents is managed by Cloudera Manager(CM).
Flume Agent configurations changes at service level are not being propagated to Agent
I.e editing Flume Agent following these steps
CM --- > Flume Service --> Configuration --> Agent Default Group --> Configuration File
The configuration doesn't seem appear in the agent configuration
Have to make the agent configuration change/s again using these steps
CM --- > Flume Service --> Instances ---> Agent ---> Configuration ---> Click Cancel for the pop up stating 'There is only one instance of this role in this service. We recommend you make configuration changes on the service configuration page instead'
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