phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-3876) Do not retry index updates until INDEX_DISABLE_TIMESTAMP is cleared
Date Tue, 23 May 2017 16:13:04 GMT

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

James Taylor reassigned PHOENIX-3876:
-------------------------------------

    Assignee: James Taylor

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

Mime
View raw message