phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (Jira)" <>
Subject [jira] [Updated] (PHOENIX-5473) Index write failures during index rebuilds should not change index table state
Date Thu, 12 Sep 2019 17:43:00 GMT


Kadir OZDEMIR updated PHOENIX-5473:
    Attachment: PHOENIX-5473.4.14-HBase-1.3.01.patch

> Index write failures during index rebuilds should not change index table state
> ------------------------------------------------------------------------------
>                 Key: PHOENIX-5473
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Kadir OZDEMIR
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0, 4.14.3
>         Attachments: PHOENIX-5473.4.14-HBase-1.3.01.patch, PHOENIX-5473.master.01.patch,
>          Time Spent: 50m
>  Remaining Estimate: 0h
> With PHOENIX-5018, index full rebuilds are done within UngroupedAggregateRegionObserver
coprocessors like index partial rebuilds. Index partial rebuilds have been only used for mutable
tables. This means that UngroupedAggregateRegionObserver had been only used for rebuilding
mutable tables. With PHOENIX-5018, UngroupedAggregateRegionObserver is now used for both
partial and full rebuilds and both immutable and mutable index tables. When an index replay
write initiated by UngroupedAggregateRegionObserver fails, the failure is handled by PhoenixIndexFailurePolicy
which disables the index table if the index write still fails after it is tried the configured
number of times. PhoenixIndexFailurePolicy is also used by the Phoenix client code. However,
PhoenixIndexFailurePolicy had been only applied to mutable tables and index write failures
never disabled an immutable index table. This behavior has changed with PHOENIX-5018 since UngroupedAggregateRegionObserver
is also used to rebuild immutable index tables. Index rebuild failures should not disable
immutable tables (and mutable tables).

This message was sent by Atlassian Jira

View raw message