hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (POWERSET)" <Jim.Keller...@microsoft.com>
Subject RE: Question on Connection Pooling
Date Wed, 22 Oct 2008 18:24:06 GMT
Connections to the master are not pooled by the client because
the only time the client needs to talk to the master is to get
the root region location (which is then cached).

Making the maximum number of cached connections configurable is
an entirely different subject. In practice, caching a "connection"
is not expensive as the connection will close its socket after
a configurable time interval of inactivity. So if later, the
client needs to talk to a cached "connection", it merely has to
reopen the socket rather than go through all the other setup.

Jim Kellerman, Powerset (Live Search, Microsoft Corporation)

> -----Original Message-----
> From: Michael Dagaev [mailto:michael.dagaev@gmail.com]
> Sent: Wednesday, October 22, 2008 3:27 AM
> To: hbase-user@hadoop.apache.org
> Subject: Question on Connection Pooling
> Hi, All
>     As I understand, HConnectionManager class pools table server
> connections (HBASE_INSTANCES) but does not pool connections to the
> master server. Is it correct? I guess it is implemented this way since
> the master serves many clients and may run of connections.  On the
> other hand, what if there are only few clients ? Doesn't it make sense
> to make this behavior configurable ?
>      I have noticed that the table server connection pool does not
> have min. and max. number of connections. Don't you think it would be
> nice to add it?
> Thank you for your cooperation,
> M.

View raw message