phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4169) Explicitly cap timeout for index disable RPC on compaction
Date Tue, 12 Sep 2017 18:22:00 GMT


James Taylor commented on PHOENIX-4169:

[~vincentpoon] - there's also an Indexer.postCompact() hook that does a cross RS call. Will
this one be ok as we're already modifying the Configuration associated with Indexer?

> Explicitly cap timeout for index disable RPC on compaction
> ----------------------------------------------------------
>                 Key: PHOENIX-4169
>                 URL:
>             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.0.98.v3.patch,
PHOENIX-4169.master.patch, PHOENIX-4169.master.v2.patch, PHOENIX-4169.master.v3.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

View raw message