hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Serega Sheypak <serega.shey...@gmail.com>
Subject Re: Connection pool Concurrency in HBase
Date Mon, 18 Aug 2014 08:49:02 GMT
I have several servlets https://en.wikipedia.org/wiki/Java_Servlet.
Servlet have a lifecycle: it's " public void init(...)" method called only
once during container startup. Servlet has SINGLE instance shared among
many web-threads.
I want to init connection pool in servlet init method and then use this
pool in doGet method of servlet.



2014-08-18 5:13 GMT+04:00 Mingtao Zhang <mail2mingtao@gmail.com>:

> We may need to know what you are planning to do with the connection pool
> to help.
>
> Mingtao Sent from iPhone
>
> > On Aug 4, 2014, at 1:44 PM, Serega Sheypak <serega.sheypak@gmail.com>
> wrote:
> >
> > Hi, I'm trying to understand how does connection pooling works in HBase.
> > I've seen that
> >
> https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HConnectionManager.html
> > is recommended to use.
> >
> > I have a servlet, it's instance shaed among many threads.
> > What is a good way to use connection pooling in this case?
> >
> > Is this
> >
> > HConnection connection = HConnectionManager.createConnection(config);
> > HTableInterface table = connection.getTable("table1");
> > try {
> >   // Use the table as needed, for a single operation and a single thread
> > } finally {
> >   table.close();
> >   connection.close();
> > }
> >
> >
> > 1. enough to reuse connection and they wouldn't be opened each time?
> > 2. why do I have to close ALL: table and connection? It's done by design?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message