Makes sense ... I will create the JIRA and attach the patch too.
Thanks,
Viral
On Fri, Oct 17, 2014 at 8:18 AM, Hari Shreedharan wrote:
> I think we should get rid of the sfWriters lock and just used synchronized
> blocks everywhere.
>
> Thanks, Hari
>
>
> On Mon, Jul 28, 2014 at 3:04 PM, Vira
I think we should get rid of the sfWriters lock and just used synchronized
blocks everywhere.
Thanks,
Hari
On Mon, Jul 28, 2014 at 3:04 PM, Viral Bajaria
wrote:
> I found the issue.
> The deadlock happens since I have 3 events that can close a file:
> 1) maxOpenFiles: set to 500
> 2) maxFile
Go ahead and file a jira. Looks like you also have the reason figured out.
Please submit a patch.
Thanks,
Hari
On Mon, Jul 28, 2014 at 3:04 PM, Viral Bajaria
wrote:
> I found the issue.
> The deadlock happens since I have 3 events that can close a file:
> 1) maxOpenFiles: set to 500
> 2) max
I have observed this again. I think this is definitely an issue because I
can repro it when running the flume agent for a few 100 files with the
above settings.
Anyone else seen this ?
Thanks,
Viral
On Mon, Jul 28, 2014 at 3:03 PM, Viral Bajaria
wrote:
> I found the issue.
>
> The deadlock ha
I found the issue.
The deadlock happens since I have 3 events that can close a file:
1) maxOpenFiles: set to 500
2) maxFileSize : set to 128MB
3) idleTimeout : set to 30 seconds
The race condition occurs when the same BucketWriter is being evicted via
the maxOpenFiles and the idleTimeout because
