[
https://issues.apache.org/jira/browse/FLUME-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459120#comment-13459120
]
Hari Shreedharan commented on FLUME-1593:
-----------------------------------------
Brock,
I am not saying we should completely ignore this issue. We might want to find a
way around it. The issue here is pretty simple:
* Txn A is about to write a txnEventRecord, checks the file - sees there is no
need to roll.
* Txn B writes something and rolls before going to write something more.
* Txn A tries to write to a closed file, fails and retries.
Am I correct in describing the problem?
I agree that a retry mechanism works, but I just feel that it could be much
simpler to implement - pretty much using a simple try-catch.
> 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
