Well, PHOENIX-4010 should not happen often. If your tables have more
regions than number of region servers you may use HBase load balancer by
tables. In that case all region servers will have some regions for each
table, so there will be no chance that region moved to the RS without hash.
To confir
I think https://issues.apache.org/jira/browse/PHOENIX-4010 may be the issue
for us, is there a way I can confirm that is the case? Can I force a region
server to update its join cache in some way, as a workaround?
Michael Prendergast
*iota IT*
Vice President / Software Engineer
(cell) 703.594.
I think you want scan_next_rate for reads and mutate_rate for writes.
> On Jul 26, 2017, at 3:53 AM, Batyrshin Alexander <0x62...@gmail.com> wrote:
>
>
>> On 26 Jul 2017, at 12:49, Batyrshin Alexander <0x62...@gmail.com> wrote:
>>
>> Hello,
>> Im collecting metrics from region servers -
>> rea
> On 26 Jul 2017, at 12:49, Batyrshin Alexander <0x62...@gmail.com> wrote:
>
> Hello,
> Im collecting metrics from region servers -
> readRequestCount/writeRequestCount.
> The problem is that Phoenix SELECT is not affects
> readRequestCount/writeRequestCount.
> Is this normal? If yes then whic
Hello,
Im collecting metrics from region servers - readRequestCount/writeRequestCount.
The problem is that Phoenix SELECT is not affects
readRequestCount/writeRequestCount.
Is this normal? If yes then which HBase metrics are affected by SELECT
statements?
