phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4785) Unable to write to table if index is made active during retry
Date Sat, 16 Jun 2018 02:48:00 GMT


Ankit Singhal commented on PHOENIX-4785:

{quote}I suppose we could set it on the client side, by writing to System.CATALOG every time
we initially get back an IndexWriteException ?
yes, client increment would be good.
{quote}The problem with doing it on the client side is, the server will set PENDING_DISABLE,
but the client could go away before updating the counter. So not sure how feasible this is.
This is fine I think because irrespective of the count we can DISABLE the table if it stays
more than phoenix.index.pending.disable.threshold in PENDING_DISABLE state.

And , another thing we should not let the index usable for queries(writes are ok) when it
is in PENDING_DISABLE state to avoid inconsistency issues even if it is for a small time.

> Unable to write to table if index is made active during retry
> -------------------------------------------------------------
>                 Key: PHOENIX-4785
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0
>            Reporter: Romil Choksi
>            Assignee: Vincent Poon
>            Priority: Blocker
>             Fix For: 5.0.0, 4.14.1
>         Attachments: PHOENIX-4785.v1.master.patch, PHOENIX-4785_test.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

View raw message