[
https://issues.apache.org/jira/browse/FLUME-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884928#comment-13884928
]
ASF subversion and git services commented on FLUME-2305:
--------------------------------------------------------
Commit 251478f2e937330d302abdcfd529ce0a6732b9af in branch refs/heads/flume-1.5
from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=251478f ]
FLUME-2305. BucketWriter#close must cancel idleFuture
(Hari Shreedharan via Jarek Jarcec Cecho)
> BucketWriter#close must cancel idleFuture
> -----------------------------------------
>
> Key: FLUME-2305
> URL: https://issues.apache.org/jira/browse/FLUME-2305
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.5.0
>
> Attachments: FLUME-2305.patch
>
>
> We use a ScheduledExecutorService to close the files after a time period. If
> the task has been submitted, the service does not cancel that task by
> default. In the ScheduledThreadPoolExecutor class: this field
> "executeExistingDelayedTasksAfterShutdown" is set to true, by default - which
> causes the task to be executed even if the executor was shutdown.
> If we don't cancel it, the agent does not die till idleTimeout even though
> every other component is stopped.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
