After user provision new flume appender, appender attempt to connect to the corresponding avro sink. If this sink is not available, Flume appender fails to initialize. All subsequent attempts to deliver logs will fail with error:
WARN o.k.k.s.a.f.a.FlumeLogAppender - Flume client wasn't initialized. Invoke method init before
This behavior is quite confusing and uncomfortable for users that setup both flume appender and sink at the same time. We need to implement logic that will try to reinitialize appender when new data from endpoint arrive.
Setup flume sink first.
Force re-init of flume appender: change something in flume appender configuration or restart operations servers.
The idea is to make sure that the destination flume sink is started before appender is configured.