Thanks for quick reply, James. We will look into UPDATE_CACHE_FREQUENCY
property. If we just replace PS with Statement, will it fix the
problem(AFAIK, Statement is not compiled)?
On Thu, Apr 12, 2018 at 10:43 PM, James Taylor
wrote:
> Try setting the
Try setting the UPDATE_CACHE_FREQUENCY table property (and configuring
the phoenix.default.update.cache.frequency system-wide property). That'll
prevent pinging the region hosting SYSTEM.CATALOG every time a query is
compiled. We've found value of even 5 seconds makes a big difference. For
more on
Hi All,
System.catalog table seems to be single region table(correct?). We are
currently facing a problem of hotspot on System.catalog table.
One of our app does around 4-5k select queries/sec. And, It is creating a
new preparedstatement everytime. I suspect that while instantiating a new
This is Phoenix 4.9, we are upgrading to 4.11 very shortly but are on 4.9 this
week.
I'll try to get a better stack trace, thanks much
World War 2 Discovery Kept Secret For Over 70 Years?!
pro.naturalhealthresponse.com
Any chance you can share the complete stacktrace you see as well as the
version of Phoenix that you're using, Lew?
This code bridges Phoenix and Avatica -- having line numbers and a
version of code to compare against will help get to the bottom of the issue.
On 4/12/18 4:48 PM, Lew Jackman
Thanks for the recommendation Josh.
This looks like our issue:
https://issues.apache.org/jira/browse/PHOENIX-4450?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16293699#comment-16293699
When we turn up the debug logging, we find this:
java.lang.RuntimeException:
Just to discard it. Might you need Java Unlimited Cryptography Extension to
be installed to deal with the cipher algorithms in your keytabs?
On Thu, 12 Apr 2018, 20:47 Yan Koyfman, wrote:
> We are attempting to create a connection to PQS (Phoenix 4.13.1) in a
> Kerberized
We are attempting to create a connection to PQS (Phoenix 4.13.1) in a
Kerberized Hbase cluster, but have been running into the following
exception. Is there something we should start with to troubleshoot?
Thanks.
Our connection string looks like this: