I use flume 1.6.0 (revision 2561a23240a71ba20bf288c7c2cda88f443c2080)
for testing to move files from local file system to s3. Only a flume
process is launched (a single jvm process). The problem is each time a
deadlock occurs between roll timer and PollingRunner threads after
running a while. A thr
rridden in your config file? A very low value could increase
> the chances of this deadlock.
>
> I'd also recommend to use the --no-reload-conf command line parameter if the
> live config reload feature is not needed.
>
> Kind regards,
> Denes
>
>
>
> On
Given a quick test (for 20k records) with patch[1] applied, the dead
lock problem looks fixed. Thanks!
[1]. https://issues.apache.org/jira/browse/FLUME-2973
On 9 February 2017 at 11:29, Chia-Hung Lin wrote:
> Thanks for the information. The maxOpenFiles value I use is the
> default
