> Hi,
>
> See this script passed into the shell:
>
> $ bin/hbase shell ~/hbase-shell-status.rb
> 11/05/26 14:57:33 INFO ipc.HBaseRPC: Using
> org.apache.hadoop.hbase.ipc.WritableRpcEngine for
> org.apache.hadoop.hbase.ipc.HMasterInterface
> 1 servers, 0 dead, 44.0000 average load
>
> HBase Shell; enter 'help<RETURN>' for list of supported commands.
> Type "exit<RETURN>" to leave the HBase Shell
> Version 0.91.0-SNAPSHOT, r1127782, Thu May 26 10:28:47 CEST 2011
>
> Why does it stay inside the shell? I would have expected the same behavior as 
> in
>
> $ echo "status" | bin/hbase shell
> HBase Shell; enter 'help<RETURN>' for list of supported commands.
> Type "exit<RETURN>" to leave the HBase Shell
> Version 0.91.0-SNAPSHOT, r1127782, Thu May 26 10:28:47 CEST 2011
>
> status
> 11/05/26 14:58:35 INFO ipc.HBaseRPC: Using
> org.apache.hadoop.hbase.ipc.WritableRpcEngine for
> org.apache.hadoop.hbase.ipc.HMasterInterface
> 1 servers, 0 dead, 44.0000 average load
> $
>
> The latter exits the shell as expected.

I think this is
http://stackoverflow.com/questions/4585313/dropping-user-to-irb-after-reading-from-pipe

>
> Also, for a while now (and I have grown blind to them) we get these
> INFO messages from the RPC classes. Should we add them to the block
> where we set the logging level already, depending on the -d switch?

The RPC logging is only in trunk, and I thought that Stack fixed it
recently (or did he just talk about doing it? I don't remember).

J-D

Reply via email to