You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2017/09/13 09:24:00 UTC
[jira] [Commented] (PHOENIX-3947) Increase scan time out for
partial index rebuild and retry only once
[ https://issues.apache.org/jira/browse/PHOENIX-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164377#comment-16164377 ]
Ankit Singhal commented on PHOENIX-3947:
----------------------------------------
[~giacomotaylor], disabling the index by setting disabled timestamp to 0 on any first exception may result in a need to rebuild all indices during RITs or any instability in HBase cluster, we should be adding some retries in round robin fashion with some delays before doing this.
> Increase scan time out for partial index rebuild and retry only once
> --------------------------------------------------------------------
>
> Key: PHOENIX-3947
> URL: https://issues.apache.org/jira/browse/PHOENIX-3947
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Samarth Jain
> Labels: globalMutableSecondaryIndex
> Fix For: 4.12.0, 4.11.1
>
> Attachments: PHOENIX-3947.patch, PHOENIX-3947_v2.patch, PHOENIX-3947_v3.patch, PHOENIX-3947_v4.patch, PHOENIX-3947_v5.patch
>
>
> The scan done from MetaDataRegionObserver needs to have a higher timeout so that it can always complete successfully. The retries should be limited to one too. Upon failure, we should disable the index and set the INDEX_DISABLE_TIMESTAMP to zero to prevent further attempts to rebuild the index (as a failure would be an indication that something is awry and manual intervention should be required to rebuild the index completely).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)