Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flume.apache.org
MIME-Version: 1.0
Date: Mon, 29 Feb 2016 10:00:42 +0200
Message-ID: 
 <CACQ=AYsXPen1vkFFFcZBV+E5JapPaZ57JhEUDLBvb3Frh99LyA@mail.gmail.com>
Subject: .tmp files are left forever if flume is crushing
From: Rani Yaroshinski <rani.yaroshinski@gmail.com>
To: user@flume.apache.org
Content-Type: multipart/alternative; boundary=001a114656589b9e72052ce40b74

--001a114656589b9e72052ce40b74
Content-Type: text/plain; charset=UTF-8

Hi,

we face issues with "orphan" .tmp files, which are leftovers from
HDFS-Sink, in the case that flume crushes before the roll conditions are
met.

I am trying to find some way to deal with those files, since it seems that
the mechanism is not complete.

Regards,
Rani

--001a114656589b9e72052ce40b74
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>we face issues with &quo=
t;orphan&quot; .tmp files, which are leftovers from HDFS-Sink, in the case =
that flume crushes before the roll conditions are met.</div><div><br></div>=
<div>I am trying to find some way to deal with those files, since it seems =
that the mechanism is not complete.</div><div><br></div><div>Regards,</div>=
<div>Rani</div></div>

--001a114656589b9e72052ce40b74--