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 one (I don't
Thanks for the information. The maxOpenFiles value I use is the
default one (I don't touch that config value in fact).
On 8 February 2017 at 15:28, Denes Arvay wrote:
> Hi,
>
> Yes, it seems to be a bug, I also bumped into it.
> It seems that the conf file poller detects change in the config file
Hi,
Yes, it seems to be a bug, I also bumped into it.
It seems that the conf file poller detects change in the config file and
tries to stop the components and in the same time HDFS sink tries to roll a
file.
It should be solved by https://issues.apache.org/jira/browse/FLUME-2973
>From your threa
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