[ https://issues.apache.org/jira/browse/PHOENIX-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani resolved PHOENIX-7306. ----------------------------------- Resolution: Fixed > Metadata lookup should be permitted only within query timeout > ------------------------------------------------------------- > > Key: PHOENIX-7306 > URL: https://issues.apache.org/jira/browse/PHOENIX-7306 > Project: Phoenix > Issue Type: Improvement > Affects Versions: 5.2.0 > Reporter: Viraj Jasani > Assignee: Viraj Jasani > Priority: Major > Fix For: 5.2.1, 5.3.0, 5.1.4 > > > When Phoenix query performs region location metadata lookup, region split or > merge could cause temporary inconsistency, which would later be resolved by > updating the region location at HBase client side as part of the Scan > operation. > However, frequent region split/merge could potentially cause the query to > fail as Phoenix client consistently checks for the region boundary for > adjacent regions while retrieving region locations for each region one by > one. Instead of throwing errors, we should allow the metadata lookup to > continue upto the given query timeout param. This would prevent Phoenix > client to get stuck forever in case of any abnormal HBase region boundary > inconsistencies. > The proposal: > * Increase default retry count for the overall metadata lookup operation. > * Do no throw Exception if the region boundaries are determined to be > overlapping. This would be resolved by HBase client internally while either > opening the scanner or resuming the scanner after receiving error from server > side. > * Do not allow metadata lookup to continue beyond the query timeout > configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)