Recent changes to bugs

Uninstantiated declared tables cause table list to fail

saarela — Wed, 03 Sep 2014 19:31:37 -0000

The HbaseSourceController::tables method calls out to the hbaseService to retrieve and populate the known tables within the hbase instance. If a table exists in META that hasn't been instantiated, the resulting TableNotFoundException through by the service causes the entire tables call to fail prematurely.

Quick fix: add an exception handler within tlist.each block to catch exceptions thrown while iterating through the table list. I have something like starting at ~line 337:

tlist = hbaseService.tableList(hbaseSourceInstance)
tlist.each {
try {
String tableName = it.nameAsString
if (hbaseService.isTableEnabled(hbaseSourceInstance, tableName)) {
onlineList << tableName
}
} catch (Exception e) {
// table was reported by hbase but didn't actually exist. Skip it.
//-
log.warn "Failed to locate table: ${e.localizedMessage}"
}
}

You end up with the following exception:

[ WARN] 13:53:47 (SLF4JLog.java:warn:189)
Exception occured while showing table details

java.lang.RuntimeException: org.apache.hadoop.hbase.TableNotFoundException: table_x
at org.apache.hadoop.hbase.client.HTableFactory.createHTableInterface(HTableFactory.java:38)
at org.apache.hadoop.hbase.client.HTablePool.createHTable(HTablePool.java:265)
at org.apache.hadoop.hbase.client.HTablePool.findOrCreateTable(HTablePool.java:195)
at org.apache.hadoop.hbase.client.HTablePool.getTable(HTablePool.java:174)
at com.nnapz.hbaseexplorer.HBaseClient.scan(HBaseClient.java:165)
at com.nnapz.hbaseexplorer.HBaseClient.scan(HBaseClient.java:246)
at com.nnapz.hbaseexplorer.HBaseClient.checkOnline(HBaseClient.java:337)
at com.nnapz.hbaseexplorer.services.HbaseService.isTableEnabled(HbaseService.groovy:241)
at com.nnapz.hbaseexplorer.controllers.HbaseSourceController$_closure14_closure31.doCall(HbaseSourceController.g
roovy:379)
at com.nnapz.hbaseexplorer.controllers.HbaseSourceController$_closure14.doCall(HbaseSourceController.groovy:377)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.hadoop.hbase.TableNotFoundException: table_x
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionMan
ager.java:1024)
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.j
ava:889)
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.j
ava:846)
at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:271)
at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:211)
at org.apache.hadoop.hbase.client.HTableFactory.createHTableInterface(HTableFactory.java:36)

#13 GString errors fall through error String check in _tables.gsp

saarela — Wed, 03 Sep 2014 19:27:19 -0000

You end up with the following exception when this occurs:

groovy.lang.MissingPropertyException: No such property: nameAsString for class: java.lang.String
at gsp_hbaseexplorer_hbaseSource_tables_gsp.run(gsp_hbaseexplorer_hbaseSource_tables_gsp.groovy:25)
at java.lang.Thread.run(Thread.java:662)

GString errors fall through error String check in _tables.gsp

saarela — Wed, 03 Sep 2014 19:23:07 -0000

in _tables.gsp there is a check to see if the given tableList is an instance of String. It is possible for this also to be a GString, which skips the test, falling through, and hitting a missing property exception within the g:each iterator below.

From the user's perspective, the table list never populates and the spinner spins forever.

Quick fix: Modify the g:if test at line 3 to read:

<g:if test="${tableList instanceof String || tableList instanceof GString}">

Pollution with extra characters like """

Nicolas — Tue, 22 Oct 2013 15:37:45 -0000

Hi Patrick,

As discussed, would it be possible for you to correct the bug in HBase Explorer where the data are polluted with extra characters like """.
(See attached screenshot)

Please let me know if you need more info.

Cheers,

Nicolas

Using hbaseexplorer

Shuheng Zhao — Wed, 14 Nov 2012 00:09:05 -0000

Hi,

Do you think you can provide example of using the hbase explorer? I have it installed but it forever gets stuck in "fetching table information". Where can I get the detailed debug info.

I am using the latest CDH4 release in a single pseudo-node installation (hbase 0.92). And in the configuration, I specify:

Quorum Client Port: 2181

Quorum Servers: localhost

HBase Master URL: localhost:60010

JobTracker URL: localhost:50030

HDFS file system URI: localhost:50070

HDFS User name: hdfs (Do I need to specify this?)

HDFS User password: (I don't think there is any)

I don't know if it is because I didn't correctly config the above entries or not. Can you help?

Invalidate table descriptors if tables are added / removed

Patrick — Tue, 21 Feb 2012 10:34:11 -0000

HTableDescriptor[] tableList(HbaseSource hbaseSourceInstance) throws MasterNotRunningException {
if (tableDescriptors == null || tableDescriptorsExpired()) {
tableDescriptors = getHBaseClient(hbaseSourceInstance).listTables()
lastRefreshTs = System.currentTimeMillis()
}
return tableDescriptors
}

boolean tableDescriptorsExpired() {
if ((System.currentTimeMillis() - lastRefreshTs) > TWO_MINUTES) {
return true;
}
return false;
}

extract method #forceRefresh and call when tables are changed

Slow scan performance

Patrick — Tue, 21 Feb 2012 10:25:18 -0000

Redundant HBaseAdmin.listTables() call for each scan.

In HBaseService#scan...

statistics

Rita Morgan — Sun, 30 Oct 2011 14:39:20 -0000

similar to hbase master console (hbasemaster:60010), it would be nice to show region servers and their statistics (how much space is being occupied by the table)

keep data persistent

Rita Morgan — Sun, 30 Oct 2011 14:36:12 -0000

When application server (tomcat) is restarted all the configuration isnt there anymore. I have to reload the hbase-site.xml. It would be nice to have a db which will keep track of the configuration.

Connection recovery problem.

EMP — Tue, 17 May 2011 15:19:07 -0000

Once the master is set to "dead", no way to recover without restarting the app.