[
https://issues.apache.org/jira/browse/PHOENIX-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177226#comment-16177226
]
James Taylor commented on PHOENIX-4214:
---------------------------------------
bq. Is there a specific exception I should be throwing to get the HBase client
to retry, without the phoenix client having to handle the exception?
I'm not sure. Best thing to do is probably play around with it. I do know that
if an IOException wraps a SQLException, we have a mechanism to turn that into
the same SQLException on the client side.
> Scans which write should not block region split or close
> --------------------------------------------------------
>
> Key: PHOENIX-4214
> URL: https://issues.apache.org/jira/browse/PHOENIX-4214
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.12.0
> Reporter: Vincent Poon
> Attachments: PHOENIX-4214.master.v1.patch,
> splitDuringUpsertSelect_wip.patch
>
>
> PHOENIX-3111 introduced a scan reference counter which is checked during
> region preSplit and preClose. However, a steady stream of UPSERT SELECT or
> DELETE can keep the count above 0 indefinitely, preventing or greatly
> delaying a region split or close.
> We should try to avoid starvation of the split / close request, and
> fail/reject queries where appropriate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
