phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-4214) Scans which write should not block region split or close
Date Sat, 16 Sep 2017 03:07:02 GMT

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

Lars Hofhansl edited comment on PHOENIX-4214 at 9/16/17 3:06 AM:
-----------------------------------------------------------------

I think unless we suspend a thread or the JVM is shutting down, the finally will get executed.
Interrupt would simply cause an exception, and finally would be executed. (the documentation,
however, is a bit unclear on this)


was (Author: lhofhansl):
I think unless we suspend a thread or the JVM is shutting down, the finally will get executed.
(the documentation, however, is a bit unclear on this)

> 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: 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)

Mime
View raw message