[
https://issues.apache.org/jira/browse/PHOENIX-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163341#comment-16163341
]
Samarth Jain commented on PHOENIX-4169:
---------------------------------------
[~vincentpoon] - it would be slightly more performant if you can have the
clonedConfig as a member variable (maybe named as compactionConfig?), instead.
There is a cost to doing a deep clone of the configuration object. You can
initialize the member variable in start() like we do for upsertSelectConfig.
> Explicitly cap timeout for index disable RPC on compaction
> ----------------------------------------------------------
>
> Key: PHOENIX-4169
> URL: https://issues.apache.org/jira/browse/PHOENIX-4169
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.12.0
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Critical
> Attachments: PHOENIX-4169.0.98.patch, PHOENIX-4169.0.98.v2.patch,
> PHOENIX-4169.master.patch, PHOENIX-4169.master.v2.patch
>
>
> In PHOENIX-3953 we're marking the mutable global index as disabled with an
> index_disable_timestamp of 0 from the compaction hook.This is a potentially a
> server-server RPC, and HConnectionManager#setServerSideHConnectionRetries
> makes it such that the HBase client config on the server side has 10 times
> the number of retries, lasting hours.
> To avoid a hung coprocessor hook, we should explicitly cap the number of
> retries here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
