How big is your cluster Arun? I would check the Master logs, look at the
actions taken while creating this table. Check the timestamps of when
region management requests are sent to the RS's and when the actions
complete. Because the salt cardinality is translated directly into region
splits, it's
Glad that it worked. I think one of our HBase committers can probably
explain that better than me. Nick?
Thanks,
James
On Tue, Jun 2, 2015 at 3:07 PM, Arun Kumaran Sabtharishi
wrote:
> James,
>
> Thanks for your reply. It worked!
> But, can you help me understand how does it make a difference ev
James,
Thanks for your reply. It worked!
But, can you help me understand how does it make a difference even when
there is no data in the system.sequence table.
Thanks,
Arun
As of 4.2.1 release, we added 256-way salting to the system.sequence
table. This might be the culprit. If you aren't yet using sequences,
you can drop the system.sequence table (you'd need to do this from the
HBase shell), set the client-side phoenix.sequence.saltBuckets to a
smaller number (or eve
It is from both code and sqlline.
On Jun 1, 2015 5:52 PM, "Nick Dimiduk" wrote:
> Is this from code, or sqlline?
>
> On Fri, May 29, 2015 at 2:42 PM, Arun Kumaran Sabtharishi <
> arun1...@gmail.com> wrote:
>
>> Upgraded Apache-phoenix-4.1.0 to 4.3.1. When connecting phoenix client
>> for the firs
Is this from code, or sqlline?
On Fri, May 29, 2015 at 2:42 PM, Arun Kumaran Sabtharishi <
arun1...@gmail.com> wrote:
> Upgraded Apache-phoenix-4.1.0 to 4.3.1. When connecting phoenix client for
> the first time, it is taking much longer time to connect than usual.
>
> Is there any workaround for
Upgraded Apache-phoenix-4.1.0 to 4.3.1. When connecting phoenix client for
the first time, it is taking much longer time to connect than usual.
Is there any workaround for connecting without taking longer time?
Note: There are more number of phoenix views and phoenix tables(4K) in the
system.
Th
