[
https://issues.apache.org/jira/browse/HBASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608143#action_12608143
]
stack commented on HBASE-705:
-----------------------------
Whats wrong with the above Billy? You get an ugly but informative message
about whats up with your table. Would you prefer that the stack trace not be
dumped into the shell? Previously, the shell used to catch exception and then
try to parse the exception to output a 'nice' message. Sometimes this worked.
Other times, the parse would hide errors (HBASE-652). Also, the shell didn't
exit, right, as it used to.
Regards the 500 error code, can I see master log? I cannot see how a client
action could bring down a master, but you never know.
> hbase shell list command does not handle RegionOfflineException
> ---------------------------------------------------------------
>
> Key: HBASE-705
> URL: https://issues.apache.org/jira/browse/HBASE-705
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Billy Pearson
> Priority: Minor
> Fix For: 0.2.0
>
>
> I get a RegionOfflineException error when trying to use the list command with
> a region offline
> {code}
> hbase(main):005:0* list
> 08/06/25 02:43:30 DEBUG client.HConnectionManager$TableServers: Cache hit in
> table locations for row <> and tableName .META.: location server
> 64.69.33.211:60020, location region name .META.,,1
> 08/06/25 02:43:30 DEBUG client.HConnectionManager$TableServers: reloading
> table servers because: region offline: webdata,,1214377950920
> 08/06/25 02:43:30 DEBUG client.HConnectionManager$TableServers: Removed
> .META.,,1 from cache because of webdata,,99999999999999
> 08/06/25 02:43:30 DEBUG client.HConnectionManager$TableServers: Found ROOT
> REGION => {NAME => '-ROOT-,,0', STARTKEY => '', ENDKEY => '', ENCODED =>
> 70236052, TABLE => {NAME => '-ROOT-', FAMILIES => [{NAME => 'info', VERSIONS
> => 1, COMPRESSION => 'NONE', IN_MEMORY => false, BLOCKCACHE => false, LENGTH
> => 2147483647, TTL => FOREVER, BLOOMFILTER => NONE}]}
> 08/06/25 02:43:40 DEBUG client.HConnectionManager$TableServers: reloading
> table servers because: region offline: webdata,,1214377950920
> 08/06/25 02:43:40 DEBUG client.HConnectionManager$TableServers: Removed
> .META.,,1 from cache because of webdata,,99999999999999
> 08/06/25 02:43:40 DEBUG client.HConnectionManager$TableServers: Found ROOT
> REGION => {NAME => '-ROOT-,,0', STARTKEY => '', ENDKEY => '', ENCODED =>
> 70236052, TABLE => {NAME => '-ROOT-', FAMILIES => [{NAME => 'info', VERSIONS
> => 1, COMPRESSION => 'NONE', IN_MEMORY => false, BLOCKCACHE => false, LENGTH
> => 2147483647, TTL => FOREVER, BLOOMFILTER => NONE}]}
> NativeException: org.apache.hadoop.hbase.client.RegionOfflineException:
> region offline: webdata,,1214377950920
> from org/apache/hadoop/hbase/client/HConnectionManager.java:446:in
> `locateRegionInMeta'
> from org/apache/hadoop/hbase/client/HConnectionManager.java:377:in
> `locateRegion'
> from org/apache/hadoop/hbase/client/HConnectionManager.java:338:in
> `locateRegion'
> from org/apache/hadoop/hbase/client/MetaScanner.java:68:in `metaScan'
> from org/apache/hadoop/hbase/client/MetaScanner.java:32:in `metaScan'
> from org/apache/hadoop/hbase/client/HConnectionManager.java:295:in
> `listTables'
> from org/apache/hadoop/hbase/client/HBaseAdmin.java:127:in
> `listTables'
> from sun/reflect/NativeMethodAccessorImpl.java:-2:in `invoke0'
> from sun/reflect/NativeMethodAccessorImpl.java:39:in `invoke'
> from sun/reflect/DelegatingMethodAccessorImpl.java:25:in `invoke'
> from java/lang/reflect/Method.java:597:in `invoke'
> from org/jruby/javasupport/JavaMethod.java:250:in
> `invokeWithExceptionHandling'
> from org/jruby/javasupport/JavaMethod.java:219:in `invoke'
> from org/jruby/javasupport/JavaClass.java:416:in `execute'
> from
> org/jruby/internal/runtime/methods/SimpleCallbackMethod.java:67:in `call'
> from org/jruby/internal/runtime/methods/DynamicMethod.java:70:in
> `call'
> ... 128 levels...
> from
> ruby.hbase_minus_671438.bin.hirbInvokermethod__23$RUBY$startOpt:-1:in `call'
> from org/jruby/internal/runtime/methods/DynamicMethod.java:74:in
> `call'
> from org/jruby/internal/runtime/methods/CompiledMethod.java:48:in
> `call'
> from org/jruby/runtime/CallSite.java:123:in `cacheAndCall'
> from org/jruby/runtime/CallSite.java:298:in `call'
> from ruby/hbase_minus_671438/bin//hbase/bin/hirb.rb:340:in `__file__'
> from ruby/hbase_minus_671438/bin//hbase/bin/hirb.rb:-1:in `__file__'
> from ruby/hbase_minus_671438/bin//hbase/bin/hirb.rb:-1:in `load'
> from org/jruby/Ruby.java:512:in `runScript'
> from org/jruby/Ruby.java:432:in `runNormally'
> from org/jruby/Ruby.java:312:in `runFromMain'
> from org/jruby/Main.java:144:in `run'
> from org/jruby/Main.java:89:in `run'
> from org/jruby/Main.java:80:in `main'
> from /hbase/bin/hirb.rb:227:in `list'
> from (hbase):6:in `binding'hbase(main):006:0>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
