You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Liyin Tang (JIRA)" <ji...@apache.org> on 2011/06/15 00:54:47 UTC

[jira] [Created] (HBASE-3988) Infinite loop for secondary master

Infinite loop for secondary master
----------------------------------

                 Key: HBASE-3988
                 URL: https://issues.apache.org/jira/browse/HBASE-3988
             Project: HBase
          Issue Type: Bug
            Reporter: Liyin Tang


There seems be a bug that the secondary master didn't come out when the primary master dead. 
Because the secondary master will be in a loop forever to watch a local variable before setting a zk watcher.
However this local variable is changed by the zk call back function.
So the secondary master will be in the infinite loop forever.

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

        

[jira] [Updated] (HBASE-3988) Infinite loop for secondary master

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

Liyin Tang updated HBASE-3988:
------------------------------

    Attachment: HBase3988_1.patch

> Infinite loop for secondary master
> ----------------------------------
>
>                 Key: HBASE-3988
>                 URL: https://issues.apache.org/jira/browse/HBASE-3988
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>         Attachments: HBase3988_1.patch
>
>
> There seems be a bug that the secondary master didn't come out when the primary master dead. 
> Because the secondary master will be in a loop forever to watch a local variable before setting a zk watcher.
> However this local variable is changed by the zk call back function.
> So the secondary master will be in the infinite loop forever.

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

        

[jira] [Resolved] (HBASE-3988) Infinite loop for secondary master

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

stack resolved HBASE-3988.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.90.4
     Hadoop Flags: [Reviewed]

Thanks for the patch Liyin.  Applied trunk and branch.

> Infinite loop for secondary master
> ----------------------------------
>
>                 Key: HBASE-3988
>                 URL: https://issues.apache.org/jira/browse/HBASE-3988
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>             Fix For: 0.90.4
>
>         Attachments: HBase3988_1.patch
>
>
> There seems be a bug that the secondary master didn't come out when the primary master dead. 
> Because the secondary master will be in a loop forever to watch a local variable before setting a zk watcher.
> However this local variable is changed by the zk call back function.
> So the secondary master will be in the infinite loop forever.

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

        

[jira] [Assigned] (HBASE-3988) Infinite loop for secondary master

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

Liyin Tang reassigned HBASE-3988:
---------------------------------

    Assignee: Liyin Tang

> Infinite loop for secondary master
> ----------------------------------
>
>                 Key: HBASE-3988
>                 URL: https://issues.apache.org/jira/browse/HBASE-3988
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>         Attachments: HBase3988_1.patch
>
>
> There seems be a bug that the secondary master didn't come out when the primary master dead. 
> Because the secondary master will be in a loop forever to watch a local variable before setting a zk watcher.
> However this local variable is changed by the zk call back function.
> So the secondary master will be in the infinite loop forever.

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