You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2017/05/23 16:14:04 UTC

[jira] [Updated] (PHOENIX-3876) Do not retry index updates until INDEX_DISABLE_TIMESTAMP is cleared

     [ https://issues.apache.org/jira/browse/PHOENIX-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-3876:
----------------------------------
    Attachment: PHOENIX-3876-wip.patch

> Do not retry index updates until INDEX_DISABLE_TIMESTAMP is cleared
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-3876
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3876
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3876-wip.patch
>
>
> Given the retry logic of HBase, if we continue to make index updates after an index write failure, we'll end up essentially blocking writes to the data table. Instead, we can simply stop issuing index updates until the partial rebuild has completed since we know then that the index table is back online.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)