[
https://issues.apache.org/jira/browse/FLUME-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459095#comment-13459095
]
Brock Noland commented on FLUME-1593:
-------------------------------------
I understand the condition has been around for some time, which is why I left
the jira as minor. I do think this should be resolved at some point since the
failure of the transaction requires rework. It's possible the rework is quite
expensive if the batch size or event size is large. Beyond that, for people who
have not worked on FileChannel, it's not obvious the error displayed in the
logs is OK. As such, this is not something we should completely ignore.
If you feel the retry mechanism is too complex, please share your thoughts.
> FileChannel race condition when log file rolls
> ----------------------------------------------
>
> Key: FLUME-1593
> URL: https://issues.apache.org/jira/browse/FLUME-1593
> Project: Flume
> Issue Type: Improvement
> Components: Channel
> Affects Versions: v1.3.0
> Reporter: Brock Noland
> Assignee: Brock Noland
> Priority: Minor
> Attachments: FLUME-1593-0.patch
>
>
> There is a non-harmful race condition when we roll a log. One thread can call
> logFiles.get(logFileIndex).{take,put,etc} while another is closing that log
> writer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
