[
https://issues.apache.org/jira/browse/PHOENIX-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664408#comment-16664408
]
Hudson commented on PHOENIX-4977:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #241 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/241/])
PHOENIX-4977 Make KillServerOnFailurePolicy a configurable option in
(vincentpoon: rev a48e42e7f639c8194db84155ce73ca9d4df25d91)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/DelegateIndexFailurePolicy.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixIndexFailurePolicy.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
> 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
> Fix For: 4.14.1
>
> Attachments: PHOENIX-4977.v1.4.x-HBase-1.4.patch,
> PHOENIX-4977.v2.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)
