phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3525) Cap automatic index rebuilding to inactive timestamp.
Date Thu, 20 Jul 2017 00:27:01 GMT


James Taylor commented on PHOENIX-3525:

[~samarthjain] - this is the JIRA we were discussing. Rather than using the timestamp at which
the index was marked active, I'd lean toward adding a new INDEX_ENABLED_TIMESTAMP instead
so that we can handle the case of keeping the index active.

> Cap automatic index rebuilding to inactive timestamp.
> -----------------------------------------------------
>                 Key: PHOENIX-3525
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Ankit Singhal
> 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