As James suggested if you set the UPDATE_CACHE_FREQUENCY table property,
the server will not be pinged for the latest metadata until the update
frequency.
Check out the altering section (https://phoenix.apache.org/)
On Sun, Feb 3, 2019 at 5:57 PM William Shen
wrote:
> Thanks for the
Thanks for the suggestions!
Jaanai - do you mean to enable trace logging on the client side or on the
server side?
James - no I have not tried setting it. I have not heard about the
configuration. Do you have a ball park suggestion on how to approach
setting this value?
On Sat, Feb 2, 2019 at
Have you tried setting UPDATE_CACHE_FREQUENCY on your tables?
On Fri, Feb 1, 2019 at 6:28 PM Jaanai Zhang wrote:
> we experimented with issuing the same query repeatedly, and we observed a
>> slow down not only on the first query
>
> I am not sure what the reasons are, perhaps you can enable
>
> we experimented with issuing the same query repeatedly, and we observed a
> slow down not only on the first query
I am not sure what the reasons are, perhaps you can enable TRACE log to
find what leads to slow, I guess that some meta information is reloaded
under highly write workload.
Thanks Jaanai. Do you know if that is expected only on the first query
against a table? For us, we experimented with issuing the same query
repeatedly, and we observed a slow down not only on the first query. Does
it make sense to preemptively load table metadata on start up to warm up
the system
It is expected when firstly query tables after establishing the connection.
Something likes loads some meta information into local cache that need take
some time, mainly including two aspects: 1. access SYSTEM.CATALOG table to
get schema information of the table 2. access the meta table of HBase
