You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2017/09/06 20:27:00 UTC

[jira] [Commented] (PHOENIX-4169) Explicitly cap timeout for index disable RPC on compaction

    [ https://issues.apache.org/jira/browse/PHOENIX-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155981#comment-16155981 ] 

Lars Hofhansl commented on PHOENIX-4169:
----------------------------------------

Marking "critical" for 4.12.

> 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
>
> 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)