[
https://issues.apache.org/jira/browse/PHOENIX-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-3947:
----------------------------------
Attachment: PHOENIX-3947_v4.patch
updated patch that addresses test failures in MutableIndexFailureIT.
[~vincentpoon], [~jamestaylor] - it would be good to get you opinions on the
below phoenix and hbase config values for index rebuild.
{code}
DEFAULT_INDEX_REBUILD_QUERY_TIMEOUT = 30000 * 60; // 30 mins
DEFAULT_INDEX_REBUILD_RPC_TIMEOUT = 30000 * 60; // 30 mins
DEFAULT_INDEX_REBUILD_CLIENT_SCANNER_TIMEOUT = 30000 * 60; // 30 mins
DEFAULT_INDEX_REBUILD_RPC_RETRIES_COUNTER = 5;
DEFAULT_INDEX_REBULD_RPC_RETRY_PAUSE = 3000; // 3 seconds
{code}
> 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
> Attachments: PHOENIX-3947.patch, PHOENIX-3947_v2.patch,
> PHOENIX-3947_v3.patch, PHOENIX-3947_v4.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)
