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 2010/06/24 18:26:50 UTC

[jira] Created: (HBASE-2785) TestScannerTimeout.test2772 is flaky

TestScannerTimeout.test2772 is flaky
------------------------------------

                 Key: HBASE-2785
                 URL: https://issues.apache.org/jira/browse/HBASE-2785
             Project: HBase
          Issue Type: Bug
            Reporter: Jean-Daniel Cryans
            Assignee: Jean-Daniel Cryans
             Fix For: 0.21.0


I knew that that test could be flaky but it seemed to work fine for a while. Basically if the region server takes too long to abort (more than 6 seconds) then the client will detect that the scanner expired instead of just moving. Find a less flaky way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (HBASE-2785) TestScannerTimeout.test2772 is flaky

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

stack commented on HBASE-2785:
------------------------------

+1

> TestScannerTimeout.test2772 is flaky
> ------------------------------------
>
>                 Key: HBASE-2785
>                 URL: https://issues.apache.org/jira/browse/HBASE-2785
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2785.patch
>
>
> I knew that that test could be flaky but it seemed to work fine for a while. Basically if the region server takes too long to abort (more than 6 seconds) then the client will detect that the scanner expired instead of just moving. Find a less flaky way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HBASE-2785) TestScannerTimeout.test2772 is flaky

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

Jean-Daniel Cryans resolved HBASE-2785.
---------------------------------------

    Hadoop Flags: [Reviewed]
      Resolution: Fixed

Thanks for the review Stack, committed to trunk.

> TestScannerTimeout.test2772 is flaky
> ------------------------------------
>
>                 Key: HBASE-2785
>                 URL: https://issues.apache.org/jira/browse/HBASE-2785
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2785.patch
>
>
> I knew that that test could be flaky but it seemed to work fine for a while. Basically if the region server takes too long to abort (more than 6 seconds) then the client will detect that the scanner expired instead of just moving. Find a less flaky way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (HBASE-2785) TestScannerTimeout.test2772 is flaky

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

Jean-Daniel Cryans updated HBASE-2785:
--------------------------------------

    Attachment: HBASE-2785.patch

This patch sets a very high timeout client-side only for the test, and I also decreased the scanner timeout for the other test back to where it was.

> TestScannerTimeout.test2772 is flaky
> ------------------------------------
>
>                 Key: HBASE-2785
>                 URL: https://issues.apache.org/jira/browse/HBASE-2785
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2785.patch
>
>
> I knew that that test could be flaky but it seemed to work fine for a while. Basically if the region server takes too long to abort (more than 6 seconds) then the client will detect that the scanner expired instead of just moving. Find a less flaky way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.