[ 
https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518947#comment-16518947
 ] 

Ankit Singhal commented on PHOENIX-4785:
----------------------------------------

bq. Just pointing out that this is another cross-RegionServer RPC that's going 
to happen. 
Yes [~elserj] , this will be cross-region in case of server writes(DELETE or 
UPSERT SELECT server) ,  otherwise it will be mostly from the client(or 
application).

 
{quote}should we be worried about a thundering-herd to the SYSTEM.CATALOG 
table's RegionServer if for a very busy system, updates to an index table all 
start failing (e.g. RS hosting a hot region for a global index "hangs")?
{quote}
In case of server writes, the number of writers will be proportional to no. of 
region/guideposts(limited by handlers and active threads executing the scan), 
such cases for UPSERT SELECT and DELETE on server are expected to be minimal 
but yeah you are right we may hit the bottleneck at sometime. Although once the 
patch to allow splitting of SYSTEM.CATALOG is out, this bottleneck will also be 
minimized, till then I'll try to spend some time on testing it on scale.

 

 

> Unable to write to table if index is made active during retry
> -------------------------------------------------------------
>
>                 Key: PHOENIX-4785
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4785
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0
>            Reporter: Romil Choksi
>            Assignee: Ankit Singhal
>            Priority: Blocker
>             Fix For: 5.0.0, 4.14.1
>
>         Attachments: PHOENIX-4785.v1.master.patch, PHOENIX-4785_test.patch, 
> PHOENIX-4785_v2.patch, PHOENIX-4785_v2_5.0-branch.patch
>
>
> After PHOENIX-4130, we are unable to write to a table if an index is made 
> ACTIVE during the retry as client timestamp is not cleared when table state 
> is changed from PENDING_DISABLE to ACTIVE even if our policy is not to block 
> writes on data table in case of write failure for index.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to