Re: Connection Pooling?

[Batyrshin Alexander]

Caching is thread starting quest, but at the end i have the same question about 
connection FAQ

> On 18 Oct 2018, at 21:06, Josh Elser  wrote:
> 
> Batyrshin, you asked about statement caching which is different than 
> connection pooling.
> 
> @JMS, yes, the FAQ is accurate (as is the majority of the rest of the 
> documentation ;))
> 
> On 10/18/18 1:14 PM, Batyrshin Alexander wrote:
>> I've already asked the same question in this thread - 
>> http://apache-phoenix-user-list.1124778.n5.nabble.com/Statements-caching-td4674.html
>>> On 18 Oct 2018, at 19:44, Jean-Marc Spaggiari >> <mailto:jean-m...@spaggiari.org>> wrote:
>>> 
>>> Hi,
>>> 
>>> Is this statement in the FAQ still valid?
>>> 
>>> "If Phoenix Connections are reused, it is possible that the underlying 
>>> HBase connection is not always left in a healthy state by the previous 
>>> user. It is better to create new Phoenix Connections to ensure that you 
>>> avoid any potential issues."
>>> https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections 
>>> <https://www.google.com/url?q=https://phoenix.apache.org/faq.html%23Should_I_pool_Phoenix_JDBC_Connections&sa=D&source=hangouts&ust=1539951968896000&usg=AFQjCNFvuOw8CmnpCcpOimhpw_DKBPH7WQ>
>>> 
>>> Thanks,
>>> 
>>> JMS

Re: Connection Pooling?

[Jean-Marc Spaggiari]

Haha ;) For once I was hoping for it to be outdated ;)

Thanks for the very prompt confirmation!

JMS

Le jeu. 18 oct. 2018 à 14:06, Josh Elser  a écrit :

> Batyrshin, you asked about statement caching which is different than
> connection pooling.
>
> @JMS, yes, the FAQ is accurate (as is the majority of the rest of the
> documentation ;))
>
> On 10/18/18 1:14 PM, Batyrshin Alexander wrote:
> > I've already asked the same question in this thread -
> >
> http://apache-phoenix-user-list.1124778.n5.nabble.com/Statements-caching-td4674.html
> >
> >> On 18 Oct 2018, at 19:44, Jean-Marc Spaggiari  >> <mailto:jean-m...@spaggiari.org>> wrote:
> >>
> >> Hi,
> >>
> >> Is this statement in the FAQ still valid?
> >>
> >> "If Phoenix Connections are reused, it is possible that the underlying
> >> HBase connection is not always left in a healthy state by the previous
> >> user. It is better to create new Phoenix Connections to ensure that
> >> you avoid any potential issues."
> >>
> https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections
> >> <
> https://www.google.com/url?q=https://phoenix.apache.org/faq.html%23Should_I_pool_Phoenix_JDBC_Connections&sa=D&source=hangouts&ust=1539951968896000&usg=AFQjCNFvuOw8CmnpCcpOimhpw_DKBPH7WQ
> >
> >>
> >> Thanks,
> >>
> >> JMS
> >
>

Re: Connection Pooling?

[Josh Elser]

Batyrshin, you asked about statement caching which is different than 
connection pooling.


@JMS, yes, the FAQ is accurate (as is the majority of the rest of the 
documentation ;))


On 10/18/18 1:14 PM, Batyrshin Alexander wrote:
I've already asked the same question in this thread - 
http://apache-phoenix-user-list.1124778.n5.nabble.com/Statements-caching-td4674.html


On 18 Oct 2018, at 19:44, Jean-Marc Spaggiari <mailto:jean-m...@spaggiari.org>> wrote:


Hi,

Is this statement in the FAQ still valid?

"If Phoenix Connections are reused, it is possible that the underlying 
HBase connection is not always left in a healthy state by the previous 
user. It is better to create new Phoenix Connections to ensure that 
you avoid any potential issues."
https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections 
<https://www.google.com/url?q=https://phoenix.apache.org/faq.html%23Should_I_pool_Phoenix_JDBC_Connections&sa=D&source=hangouts&ust=1539951968896000&usg=AFQjCNFvuOw8CmnpCcpOimhpw_DKBPH7WQ>


Thanks,

JMS

Re: Connection Pooling?

[Batyrshin Alexander]

I've already asked the same question in this thread - 
http://apache-phoenix-user-list.1124778.n5.nabble.com/Statements-caching-td4674.html

> On 18 Oct 2018, at 19:44, Jean-Marc Spaggiari  wrote:
> 
> Hi,
> 
> Is this statement in the FAQ still valid?
> 
> "If Phoenix Connections are reused, it is possible that the underlying HBase 
> connection is not always left in a healthy state by the previous user. It is 
> better to create new Phoenix Connections to ensure that you avoid any 
> potential issues."
>  https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections 
> 
> 
> Thanks,
> 
> JMS

Connection Pooling?

[Jean-Marc Spaggiari]

Hi,

Is this statement in the FAQ still valid?

"If Phoenix Connections are reused, it is possible that the underlying
HBase connection is not always left in a healthy state by the previous
user. It is better to create new Phoenix Connections to ensure that you
avoid any potential issues."
 https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections


Thanks,

JMS

Re: Connection pooling in Phoenix ?

[Dmitry Goldenberg]

Great. Thanks, Ravi, and James.

- Dmitry

On Thu, Nov 5, 2015 at 5:36 PM, Ravi Kiran 
wrote:

> Hi Dmitry,
>
> James has answered this couple of times in earlier threads. Found this
> useful. Hope it helps!
>
>  https://groups.google.com/forum/#!topic/phoenix-hbase-user/lL-SVFeFpNg
>  https://groups.google.com/forum/#!topic/phoenix-hbase-user/U3hCUhRTZV8
>
> Regards
> Ravi
>
> On Thu, Nov 5, 2015 at 2:21 PM, Dmitry Goldenberg <
> dgoldenberg...@gmail.com> wrote:
>
>> Hi,
>>
>> Could someone provide an overview of connection pooling vis a vis Phoenix?
>>
>> 1. Does Phoenix do connection pooling under the covers? We currently just
>> create connections and then close them once we're done with a given request
>> which doesn't seem to drastically curtail performance. However, we've not
>> truly stressed the system just yet.  We're wondering if indeed we should go
>> with connection pooling, from the performance perspective.
>>
>> 2. If there's no built-in connection pooling, does it make sense to
>> integrate something like Apache Dbcp?
>>
>> Thanks.
>>
>
>

Re: Connection pooling in Phoenix ?

[Ravi Kiran]

Hi Dmitry,

James has answered this couple of times in earlier threads. Found this
useful. Hope it helps!

 https://groups.google.com/forum/#!topic/phoenix-hbase-user/lL-SVFeFpNg
 https://groups.google.com/forum/#!topic/phoenix-hbase-user/U3hCUhRTZV8

Regards
Ravi

On Thu, Nov 5, 2015 at 2:21 PM, Dmitry Goldenberg 
wrote:

> Hi,
>
> Could someone provide an overview of connection pooling vis a vis Phoenix?
>
> 1. Does Phoenix do connection pooling under the covers? We currently just
> create connections and then close them once we're done with a given request
> which doesn't seem to drastically curtail performance. However, we've not
> truly stressed the system just yet.  We're wondering if indeed we should go
> with connection pooling, from the performance perspective.
>
> 2. If there's no built-in connection pooling, does it make sense to
> integrate something like Apache Dbcp?
>
> Thanks.
>

Connection pooling in Phoenix ?

[Dmitry Goldenberg]

Hi,

Could someone provide an overview of connection pooling vis a vis Phoenix?

1. Does Phoenix do connection pooling under the covers? We currently just
create connections and then close them once we're done with a given request
which doesn't seem to drastically curtail performance. However, we've not
truly stressed the system just yet.  We're wondering if indeed we should go
with connection pooling, from the performance perspective.

2. If there's no built-in connection pooling, does it make sense to
integrate something like Apache Dbcp?

Thanks.

Phoenix connection pooling in a multi-tenant environment‏

[mak shah]

Phoenix is an embedded driver and it automatically manages connection pooling. 
In case of multi-tenancy, tenant-specific connections are created by specifying 
tenantId property in JDBC. Does phoenix still automatically handle connection 
pooling, if I create multiple connections each with separate tenantId ? I am 
expecting thousands of tenant-specific connections in my application.Thanks,- 
Mak