phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5291) Some cases where Phoenix does close scanners
Date Wed, 22 May 2019 16:20:00 GMT


Lars Hofhansl commented on PHOENIX-5291:

I'll file an HBase jira to make this generally less fickle. The main problem is that all coprocessors
that run with lease removed can do a lot of damage now. And even with the lease in place they
can replace the passes scanner, in which case the it won't be closed anymore. That was bad
before, but now it's a much worse.

I'll dig through the Phoenix code a bit more.

> Some cases where Phoenix does close scanners
> --------------------------------------------
>                 Key: PHOENIX-5291
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 4.14.1, 4.14.2
>            Reporter: Lars Hofhansl
>            Priority: Critical
>         Attachments: 5291.txt
> With HBase 1.5 and later this is a disaster, as it causes the wrong reference counting
of HFiles in HBase, and those subsequently will *never* be removed until the region closes
and reopens for any reason.
> We found at least two cases... See comments below.

This message was sent by Atlassian JIRA

View raw message