[
https://issues.apache.org/jira/browse/PHOENIX-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652361#comment-16652361
]
Geoffrey Jacoby commented on PHOENIX-4963:
------------------------------------------
A comment explaining why TABLE_ALREADY_EXISTS is being used would be nice,
otherwise +1.
> 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
> Attachments: PHOENIX-4963.v1.master.patch,
> PHOENIX-4963.v2.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)
