You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/07/25 07:07:49 UTC
[jira] [Updated] (HBASE-9025) Potential Thread safety issue in
MetaScanner
[ https://issues.apache.org/jira/browse/HBASE-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-9025:
---------------------------------
Summary: Potential Thread safety issue in MetaScanner (was: Thread safety issue in MetaScanner)
> Potential Thread safety issue in MetaScanner
> --------------------------------------------
>
> Key: HBASE-9025
> URL: https://issues.apache.org/jira/browse/HBASE-9025
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.9
> Reporter: Lars Hofhansl
>
> I just saw this in a test run in 0.94:
> {code}
> Stacktrace
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:324)
> at java.util.TreeMap.get(TreeMap.java:255)
> at org.apache.hadoop.hbase.util.TestHBaseFsck.testSplitDaughtersNotInMeta(TestHBaseFsck.java:1346)
> ...
> {code}
> The TreeMap in question here is actually returned from {{HTable.getRegionLocations()}}, which in turns calls {{MetaScanner.allTableRegions(getConfiguration(), getTableName(), false);}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira