[
https://issues.apache.org/jira/browse/PHOENIX-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652642#comment-16652642
]
Hadoop QA commented on PHOENIX-4963:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12944234/PHOENIX-4963.v3.master.patch
against master branch at commit e07e04a54a6720a0ba8e7a806cd98a2ebc8b2d17.
ATTACHMENT ID: 12944234
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2093//console
This message is automatically generated.
> Do not throw when transitioning to PENDING_DISABLE if index is already
> disabled
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-4963
> URL: https://issues.apache.org/jira/browse/PHOENIX-4963
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Critical
> Fix For: 4.14.1
>
> Attachments: PHOENIX-4963.v1.master.patch,
> PHOENIX-4963.v2.master.patch, PHOENIX-4963.v3.master.patch
>
>
> When multiple clients get index write failures, they may attempt to
> transition to PENDING_DISABLE concurrently. A race condition can cause one
> to exhaust its retries first and transition the index to DISABLE, and another
> client to then attempt to transition from DISABLE to PENDING_DISABLE.
> Currently this is causing an exception to get thrown, leading to the
> KillServerOnFailurePolicy getting activated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
