phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Poon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4977) Make KillServerOnFailurePolicy a configurable option in PhoenixIndexFailurePolicy
Date Tue, 23 Oct 2018 23:05:00 GMT

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

Vincent Poon updated PHOENIX-4977:
----------------------------------
    Attachment: PHOENIX-4977.v1.4.x-HBase-1.4.patch

> Make KillServerOnFailurePolicy a configurable option in PhoenixIndexFailurePolicy
> ---------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4977
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4977
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0
>            Reporter: Vincent Poon
>            Assignee: Vincent Poon
>            Priority: Major
>         Attachments: PHOENIX-4977.v1.4.x-HBase-1.4.patch
>
>
> Currently PhoenixIndexFailurePolicy, which is the default policy, delegates to KillServerOnFailurePolicy.
 This is hardcoded in the constructor.  Apparently this was added for a specific use case,
BLOCK_DATA_TABLE_WRITES_ON_WRITE_FAILURE, and the policy itself derives from the days where
forcing a RS kill was in effect the way to 'rebuild' the index via WAL replay.
> There are still cases where it's applicable, such as when Syscat itself cannot be updated
in order to e.g. disable an index.  However, killing the RS may be too aggressive for some,
who might prefer a temporarily out of sync index to a potentially cascading wave of aborts.
> We should add a config option to control this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message