You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2012/08/17 01:49:38 UTC

[jira] [Created] (BIGTOP-691) flume gets killed too fast when the service is asked to stop

Roman Shaposhnik created BIGTOP-691:
---------------------------------------

             Summary: flume gets killed too fast when the service is asked to stop
                 Key: BIGTOP-691
                 URL: https://issues.apache.org/jira/browse/BIGTOP-691
             Project: Bigtop
          Issue Type: Bug
          Components: Init scripts
    Affects Versions: 0.4.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.5.0


The flume stop script does the following:

kill -TERM ${FLUME_PID} &>/dev/null
sleep 5
kill -KILL ${FLUME_PID} &>/dev/null

It is not recommended to kill -9 flume while it is shutting down.

The correct approach is to poll to see if the pid is up every second or so, after sending the intitial TERM signal, then after some long period of time (60 seconds) if the pid is still alive then kill -9 would be appropriate.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-691) flume gets killed too fast when the service is asked to stop

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-691:
------------------------------------

    Attachment: BIGTOP-691.patch.txt
    
> flume gets killed too fast when the service is asked to stop
> ------------------------------------------------------------
>
>                 Key: BIGTOP-691
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-691
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Init scripts
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-691.patch.txt
>
>
> The flume stop script does the following:
> kill -TERM ${FLUME_PID} &>/dev/null
> sleep 5
> kill -KILL ${FLUME_PID} &>/dev/null
> It is not recommended to kill -9 flume while it is shutting down.
> The correct approach is to poll to see if the pid is up every second or so, after sending the intitial TERM signal, then after some long period of time (60 seconds) if the pid is still alive then kill -9 would be appropriate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-691) flume gets killed too fast when the service is asked to stop

Posted by "Patrick Taylor Ramsey (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436914#comment-13436914 ] 

Patrick Taylor Ramsey commented on BIGTOP-691:
----------------------------------------------

+1 LGTM.
                
> flume gets killed too fast when the service is asked to stop
> ------------------------------------------------------------
>
>                 Key: BIGTOP-691
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-691
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Init scripts
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-691.patch.txt
>
>
> The flume stop script does the following:
> kill -TERM ${FLUME_PID} &>/dev/null
> sleep 5
> kill -KILL ${FLUME_PID} &>/dev/null
> It is not recommended to kill -9 flume while it is shutting down.
> The correct approach is to poll to see if the pid is up every second or so, after sending the intitial TERM signal, then after some long period of time (60 seconds) if the pid is still alive then kill -9 would be appropriate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (BIGTOP-691) flume gets killed too fast when the service is asked to stop

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik resolved BIGTOP-691.
-------------------------------------

    Resolution: Fixed
    
> flume gets killed too fast when the service is asked to stop
> ------------------------------------------------------------
>
>                 Key: BIGTOP-691
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-691
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Init scripts
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-691.patch.txt
>
>
> The flume stop script does the following:
> kill -TERM ${FLUME_PID} &>/dev/null
> sleep 5
> kill -KILL ${FLUME_PID} &>/dev/null
> It is not recommended to kill -9 flume while it is shutting down.
> The correct approach is to poll to see if the pid is up every second or so, after sending the intitial TERM signal, then after some long period of time (60 seconds) if the pid is still alive then kill -9 would be appropriate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira