[
https://issues.apache.org/jira/browse/FLUME-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Shreedharan updated FLUME-2305:
------------------------------------
Description:
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.
Environment: (was: 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. )
> 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
>
> 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)
