You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2014/04/01 20:09:27 UTC

[jira] [Resolved] (FLUME-2354) Fix possible race condition in Cursor

     [ https://issues.apache.org/jira/browse/FLUME-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Shreedharan resolved FLUME-2354.
-------------------------------------

    Resolution: Won't Fix

Flume 0.9.x is no longer maintained. These versions will not get any fixes committed, nor will there be any further release.

Please migrate to Flume 1.4 (aka Flume NG) as soon as possible. 

> Fix possible race condition in Cursor
> -------------------------------------
>
>                 Key: FLUME-2354
>                 URL: https://issues.apache.org/jira/browse/FLUME-2354
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v0.9.5
>            Reporter: hailinzeng
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> It is possible to seen a late modification timestamp change after file size has changed. 
> // host-time file-size file-modified-time
> // 12:00    50k    12:00
> // 12:01    51k    12:00
> // 12:02    51k    12:01 <- 
> If this happens, and nothing new is written after sleepped 1s in line 293, Cursor will resetRAF and read this file from beginning again !



--
This message was sent by Atlassian JIRA
(v6.2#6252)