phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Created] (PHOENIX-3949) Stop index writing until index_disable_timestamp is cleared
Date Fri, 16 Jun 2017 00:24:00 GMT
James Taylor created PHOENIX-3949:

             Summary: Stop index writing until index_disable_timestamp is cleared
                 Key: PHOENIX-3949
             Project: Phoenix
          Issue Type: Bug
            Reporter: James Taylor

An index can be configured to remain online if a write failure occurs as our partial index
rebuilder will kick in upon failure and catch it up. However, by keeping the index active,
subsequent writes to the data table will likely time out when they attempt to update the index
given the current timeouts (see PHOENIX-3948).

An alternative would be to hold off on any index updates until the partial index rebuilder
has completed the catch up process and cleared the INDEX_DISABLED_TIMESTAMP field. This creates
a race condition with writes that happen right as the INDEX_DISABLED_TIMESTAMP field is cleared.
We could run a catchup query on the partial index rebuild after the field is cleared to ensure
we find rows that were committed before the regular index maintenance starts again.

This message was sent by Atlassian JIRA

View raw message