You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2007/07/16 20:35:04 UTC
[jira] Created: (HADOOP-1616) [hbase] Sporadic TestTable failures
[hbase] Sporadic TestTable failures
-----------------------------------
Key: HADOOP-1616
URL: https://issues.apache.org/jira/browse/HADOOP-1616
Project: Hadoop
Issue Type: Bug
Components: contrib/hbase
Reporter: stack
Assignee: stack
Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1616) [hbase] Sporadic TestTable failures
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-1616:
--------------------------
Attachment: hadoop-1616-v2.patch
V2. Passes all tests.
> [hbase] Sporadic TestTable failures
> -----------------------------------
>
> Key: HADOOP-1616
> URL: https://issues.apache.org/jira/browse/HADOOP-1616
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Attachments: hadoop-1616-v2.patch, hadoop-1616.patch
>
>
> Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1616) [hbase] Sporadic TestTable failures
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-1616:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed patch.
> [hbase] Sporadic TestTable failures
> -----------------------------------
>
> Key: HADOOP-1616
> URL: https://issues.apache.org/jira/browse/HADOOP-1616
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Attachments: hadoop-1616-v2.patch, hadoop-1616.patch
>
>
> Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1616) [hbase] Sporadic TestTable failures
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-1616:
--------------------------
Attachment: hadoop-1616.patch
Found leaking file handles. Was (on some machines) getting in the way of our running two tests of a TestCase on MiniHBaseCluster.
HADOOP-1616 [hbase] Sporadic TestTable failures
Found a couple of leaking file handles that on some machines
prevented hdfs client shutting down its lease checker. Was
stopping us moving on to next unit test in a Test Case.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/MiniHBaseCluster.java
Add close of filesystem. Will print out any leaking filehandles.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/TestScanner2.java
Close region log.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/TestTableMapReduce.java
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/AbstractMergeTestBase.java
(createNewHRegion): Signature changed.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/HBaseTestCase.java
(createNewHRegion): Refactored to use HRegion.createNewRegion.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/TestHLog.java
Close and delete hlog.
M src/contrib/hbase/src/test/org/apache/hadoop/hbase/TestHRegion.java
(tearDown): Added. Close hlog.
M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HLog.java
Made logging more informative. javadoc and formatting changes.
M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HMaster.java
(createTable): Close temporary region logs.
M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HRegion.java
Javadoc.
> [hbase] Sporadic TestTable failures
> -----------------------------------
>
> Key: HADOOP-1616
> URL: https://issues.apache.org/jira/browse/HADOOP-1616
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Attachments: hadoop-1616.patch
>
>
> Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1616) [hbase] Sporadic TestTable failures
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513131 ]
Hadoop QA commented on HADOOP-1616:
-----------------------------------
-1, build or testing failed
2 attempts failed to build and test the latest attachment http://issues.apache.org/jira/secure/attachment/12361935/hadoop-1616-v2.patch against trunk revision r556754.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/424/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/424/console
Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.
> [hbase] Sporadic TestTable failures
> -----------------------------------
>
> Key: HADOOP-1616
> URL: https://issues.apache.org/jira/browse/HADOOP-1616
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Attachments: hadoop-1616-v2.patch, hadoop-1616.patch
>
>
> Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1616) [hbase] Sporadic TestTable failures
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-1616:
--------------------------
Status: Patch Available (was: Open)
Trying patch against hudson (though the poor fella seems a little erratic today).
> [hbase] Sporadic TestTable failures
> -----------------------------------
>
> Key: HADOOP-1616
> URL: https://issues.apache.org/jira/browse/HADOOP-1616
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Attachments: hadoop-1616-v2.patch, hadoop-1616.patch
>
>
> Nightly failed in TestTable (though 'patch available' build passed and it passes all tests locally). The nightly failure has been reproduced on a machine here so looking into it (DFSClient leaseChecker thread is staying up though minidfs has been shutdown -- it then goes on to complain it can't connect to the destroyed 'remote' minidfs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.