You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2012/05/10 19:58:52 UTC

[jira] [Created] (AMBARI-211) Same kick timeout is not appropriate for all kind of nodes.

Jitendra Nath Pandey created AMBARI-211:
-------------------------------------------

             Summary: Same kick timeout is not appropriate for all kind of nodes.
                 Key: AMBARI-211
                 URL: https://issues.apache.org/jira/browse/AMBARI-211
             Project: Ambari
          Issue Type: Bug
          Components: controller
            Reporter: Jitendra Nath Pandey
            Assignee: Jitendra Nath Pandey


The kick timeout becomes too short for slower machines. The fix will be to detect if the agent is busy and don't timeout if agent is still processing, previous kick.

--
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] (AMBARI-211) Same kick timeout is not appropriate for all kind of nodes.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated AMBARI-211:
----------------------------------------

    Attachment: AMBARI-211.1.patch
    
> Same kick timeout is not appropriate for all kind of nodes.
> -----------------------------------------------------------
>
>                 Key: AMBARI-211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-211
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: AMBARI-211.1.patch
>
>
> The kick timeout becomes too short for slower machines. The fix will be to detect if the agent is busy and don't timeout if agent is still processing, previous kick.

--
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] (AMBARI-211) Same kick timeout is not appropriate for all kind of nodes.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey resolved AMBARI-211.
-----------------------------------------

    Resolution: Fixed

Committed as part of AMBARI-237.
                
> Same kick timeout is not appropriate for all kind of nodes.
> -----------------------------------------------------------
>
>                 Key: AMBARI-211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-211
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: AMBARI-211.1.patch
>
>
> The kick timeout becomes too short for slower machines. The fix will be to detect if the agent is busy and don't timeout if agent is still processing, previous kick.

--
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] (AMBARI-211) Same kick timeout is not appropriate for all kind of nodes.

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-211:
-------------------------------------------

    Affects Version/s: 0.9.0
    
> Same kick timeout is not appropriate for all kind of nodes.
> -----------------------------------------------------------
>
>                 Key: AMBARI-211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-211
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 0.9.0
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-211.1.patch
>
>
> The kick timeout becomes too short for slower machines. The fix will be to detect if the agent is busy and don't timeout if agent is still processing, previous kick.

--
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] (AMBARI-211) Same kick timeout is not appropriate for all kind of nodes.

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-211:
-------------------------------------------

    Fix Version/s: 0.9.0
    
> Same kick timeout is not appropriate for all kind of nodes.
> -----------------------------------------------------------
>
>                 Key: AMBARI-211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-211
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-211.1.patch
>
>
> The kick timeout becomes too short for slower machines. The fix will be to detect if the agent is busy and don't timeout if agent is still processing, previous kick.

--
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