A sink runner and the sink are build from the configuration and started
by the lifecycle manager. The runner then regularly calls process on the
Sinks and sources are not required to be multithreaded, as they are
normally exclusively accessed by their runners. The exception to this is
the lifecycle manager which may call start/stop pretty much whenever.
On 08/03/2012 04:24 AM, Mohit Anchlia wrote:
> Trying to understand how flume sink invocation works. I see
> HBaseSink.java has start and stop, is this object created once or is
> this object created for every event call to sink?
> Also, who calls start,process and stop?