You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2011/04/21 00:14:05 UTC

[jira] [Created] (HBASE-3805) Log RegionState that are processed too late in the master

Log RegionState that are processed too late in the master 
----------------------------------------------------------

                 Key: HBASE-3805
                 URL: https://issues.apache.org/jira/browse/HBASE-3805
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 0.90.2
            Reporter: Jean-Daniel Cryans
            Assignee: Jean-Daniel Cryans
            Priority: Minor
             Fix For: 0.90.3


Working on all the weird delayed processing in the master, I saw that it was hard to figure when a zookeeper event is processed too late. For example, cases where the processing of the events gets too slow and the master takes more than a minute after the event is triggered in the region server to get to it's processing.

We should at least print that out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-3805) Log RegionState that are processed too late in the master

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-3805:
--------------------------------------

    Attachment: HBASE-3805.patch

I was hoping to put more debugging like when the executor starts working on a task and if it's late, but couldn't find a way for that. So this patch only checks if the RegionTransitionData's stamp is more than 15 seconds old and prints that out if it's the case.

> Log RegionState that are processed too late in the master 
> ----------------------------------------------------------
>
>                 Key: HBASE-3805
>                 URL: https://issues.apache.org/jira/browse/HBASE-3805
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.90.3
>
>         Attachments: HBASE-3805.patch
>
>
> Working on all the weird delayed processing in the master, I saw that it was hard to figure when a zookeeper event is processed too late. For example, cases where the processing of the events gets too slow and the master takes more than a minute after the event is triggered in the region server to get to it's processing.
> We should at least print that out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-3805) Log RegionState that are processed too late in the master

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved HBASE-3805.
---------------------------------------

    Resolution: Fixed

Committed the additional logging.

> Log RegionState that are processed too late in the master 
> ----------------------------------------------------------
>
>                 Key: HBASE-3805
>                 URL: https://issues.apache.org/jira/browse/HBASE-3805
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.90.3
>
>         Attachments: HBASE-3805.patch
>
>
> Working on all the weird delayed processing in the master, I saw that it was hard to figure when a zookeeper event is processed too late. For example, cases where the processing of the events gets too slow and the master takes more than a minute after the event is triggered in the region server to get to it's processing.
> We should at least print that out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-3805) Log RegionState that are processed too late in the master

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027256#comment-13027256 ] 

Hudson commented on HBASE-3805:
-------------------------------

Integrated in HBase-TRUNK #1888 (See [https://builds.apache.org/hudson/job/HBase-TRUNK/1888/])
    

> Log RegionState that are processed too late in the master 
> ----------------------------------------------------------
>
>                 Key: HBASE-3805
>                 URL: https://issues.apache.org/jira/browse/HBASE-3805
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.90.3
>
>         Attachments: HBASE-3805.patch
>
>
> Working on all the weird delayed processing in the master, I saw that it was hard to figure when a zookeeper event is processed too late. For example, cases where the processing of the events gets too slow and the master takes more than a minute after the event is triggered in the region server to get to it's processing.
> We should at least print that out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira