phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-3525) Cap automatic index rebuilding to inactive timestamp
Date Tue, 08 Aug 2017 02:12:00 GMT


James Taylor updated PHOENIX-3525:
    Attachment: PHOENIX-3525_v1.patch

Simplified patch (doesn't change any client APIs):
- delays rebuild until a configurable period of time after setting index status to INACTIVE
- detects whether another write failure occurred while rebuilder is running (through checkAndPut
and passing expected INDEX_DISABLE_TIMESTAMP). In this case, it will run again rather than
activate it.
- sets upper time range on query so that writes can continue on data table without impacting

We can improve the handling of the case of leaving the index active in a follow up patch.

Please review [~samarthjain].

> Cap automatic index rebuilding to inactive timestamp
> ----------------------------------------------------
>                 Key: PHOENIX-3525
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Ankit Singhal
>            Assignee: James Taylor
>             Fix For: 4.12.0, 4.11.1
>         Attachments: PHOENIX-3525_v1.patch, PHOENIX-3525_wip2.patch, PHOENIX-3525_wip.patch
> From [] review comment on 
> For automatic rebuilding ,DISABLED_TIMESTAMP is lower bound but there is no upper bound
so we are going rebuild all the new writes written after DISABLED_TIMESTAMP even though indexes
updated properly. So we can introduce an upper bound of time where we are going to start a
rebuild thread so we can limit the data to rebuild. In case If there are frequent writes then
we can increment the rebuild period exponentially

This message was sent by Atlassian JIRA

View raw message