Yong:
Can you post full stack trace so that we can diagnose the problem ?

Cheers


On Tue, Oct 22, 2013 at 11:01 AM, yonghu <yongyong...@gmail.com> wrote:

> Gray,
>
> Finally, I saw the error messages. ERROR:
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed
> 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: Coprocessor:
>
> 'org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionEnvironment@303a60
> '
> threw: 'java.lang.UnsupportedOperationException: Immutable Configuration'
> and has been removed from the active coprocessor set.
>
> I will try different approach as Ted mentioned.
>
>
> On Tue, Oct 22, 2013 at 7:49 PM, yonghu <yongyong...@gmail.com> wrote:
>
> > Gray
> >
> > Thanks for your response. I tried your approach. But it did not work. The
> > HBase just stalled, no messages, nothing happened. By the way, my hbase
> > version is 0.94.12.
> >
> >
> >
> > On Tue, Oct 22, 2013 at 7:34 PM, Gary Helmling <ghelml...@gmail.com
> >wrote:
> >
> >> Within a coprocessor, you can just use the CoprocessorEnvironment
> instance
> >> passed to start() method or any of the pre/post hooks, and call
> >> CoprocessorEnvironment.getTable(byte[] tablename).
> >>
> >>
> >> On Tue, Oct 22, 2013 at 9:41 AM, Ted Yu <yuzhih...@gmail.com> wrote:
> >>
> >> > Take a look at http://hbase.apache.org/book.html#client.connections ,
> >> > especially 9.3.1.1.
> >> >
> >> >
> >> > On Tue, Oct 22, 2013 at 9:37 AM, yonghu <yongyong...@gmail.com>
> wrote:
> >> >
> >> > > Hello,
> >> > >
> >> > > In the oldest verison of HBase , I can get the HTableInterface by
> >> > > HTablePool.getTable() method. However, in the latest Hbase
> >> > version0.94.12,
> >> > > HTablePool is deprecated. So, I tried to use HConnectionManager to
> >> create
> >> > > HTableInterface, but it does not work. Can anyone tell me how to
> >> create
> >> > > HTableInterface in new HBase version? By the way, there is no error
> >> > message
> >> > > when I run coprocessor.
> >> > >
> >> > > regards!
> >> > >
> >> > > Yong
> >> > >
> >> >
> >>
> >
> >
>

Reply via email to