You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/06/22 23:40:56 UTC
[jira] Created: (HBASE-2768) TestFilter tearDown is in wrong order
TestFilter tearDown is in wrong order
-------------------------------------
Key: HBASE-2768
URL: https://issues.apache.org/jira/browse/HBASE-2768
Project: HBase
Issue Type: Test
Affects Versions: 0.21.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Fix For: 0.21.0
Attachments: hbase-2768.txt
The teardown of TestFilter calls super.tearDown() before closing the region. So, the region is closed after its files have been deleted under it, which causes the tearDown to throw exceptions after HBASE-2729 gets committed. Reversing the teardown order fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2768) TestFilter tearDown is in wrong
order
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881384#action_12881384 ]
stack commented on HBASE-2768:
------------------------------
duh! +1
> TestFilter tearDown is in wrong order
> -------------------------------------
>
> Key: HBASE-2768
> URL: https://issues.apache.org/jira/browse/HBASE-2768
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.21.0
>
> Attachments: hbase-2768.txt
>
>
> The teardown of TestFilter calls super.tearDown() before closing the region. So, the region is closed after its files have been deleted under it, which causes the tearDown to throw exceptions after HBASE-2729 gets committed. Reversing the teardown order fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-2768) TestFilter tearDown is in wrong order
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved HBASE-2768.
--------------------------------
Hadoop Flags: [Reviewed]
Resolution: Fixed
Committed to trunk and 0.89.20100621 (was causing red builds on my branch hudson, we should hopefully release off a green one!)
> TestFilter tearDown is in wrong order
> -------------------------------------
>
> Key: HBASE-2768
> URL: https://issues.apache.org/jira/browse/HBASE-2768
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.21.0
>
> Attachments: hbase-2768.txt
>
>
> The teardown of TestFilter calls super.tearDown() before closing the region. So, the region is closed after its files have been deleted under it, which causes the tearDown to throw exceptions after HBASE-2729 gets committed. Reversing the teardown order fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2768) TestFilter tearDown is in wrong order
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HBASE-2768:
-------------------------------
Attachment: hbase-2768.txt
> TestFilter tearDown is in wrong order
> -------------------------------------
>
> Key: HBASE-2768
> URL: https://issues.apache.org/jira/browse/HBASE-2768
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.21.0
>
> Attachments: hbase-2768.txt
>
>
> The teardown of TestFilter calls super.tearDown() before closing the region. So, the region is closed after its files have been deleted under it, which causes the tearDown to throw exceptions after HBASE-2729 gets committed. Reversing the teardown order fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.