[ 
https://issues.apache.org/jira/browse/FLUME-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916553#comment-13916553
 ] 

ASF subversion and git services commented on FLUME-2328:
--------------------------------------------------------

Commit c9b531e70a655e331f18012d3c24614ac2c66b75 in flume's branch 
refs/heads/trunk from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=c9b531e ]

FLUME-2328: FileChannel Dual Checkpoint Backup Thread not released on 
Application stop

(Hari Shreedharan via Jarek Jarcec Cecho)


> FileChannel Dual Checkpoint Backup Thread not released on Application stop
> --------------------------------------------------------------------------
>
>                 Key: FLUME-2328
>                 URL: https://issues.apache.org/jira/browse/FLUME-2328
>             Project: Flume
>          Issue Type: Bug
>          Components: File Channel
>    Affects Versions: v1.4.0
>            Reporter: Arun
>            Assignee: Hari Shreedharan
>             Fix For: v1.5.0
>
>         Attachments: FLUME-2328.patch
>
>
> In my application wired the filechannel with dual checkpoint enabled. Even 
> after calling application.stop() i can see checkpoint backup thread is still 
> in waiting state.
> "[channel=c1] - CheckpointBackUpThread" prio=6 tid=0x3a069400 nid=0x8a4 
> waiting on condition [0x3b17f000]
> Since i am usign java service wrapper to run application and for stopping 
> service i am waiting all user threads to be released, service is not stopping 
> gracefully even after waiting for 5 mins.
> in code i can see checkpointBackUpExecutor is started 
> if (shouldBackup) { 
>       checkpointBackUpExecutor = Executors.newSingleThreadExecutor(         
> new ThreadFactoryBuilder().setNameFormat(           getName() + " - 
> CheckpointBackUpThread").build());     
> } else {       checkpointBackUpExecutor = null;     } 
> ....
> there is no shutdown call for checkpointBackUpExecutor in anywhere in 
> EventQueueBackingStoreFile
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to