[
https://issues.apache.org/jira/browse/PHOENIX-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935010#comment-14935010
]
Dan Meany commented on PHOENIX-2291:
------------------------------------
I am going to try increasing the server side timeout for the join cache from
the default of 30 sec. It does not happen every time. Given these are small
tables with indexes, maybe with the calcite integration joins will perform
better.
> Error: Could not find hash cache for joinId
> -------------------------------------------
>
> Key: PHOENIX-2291
> URL: https://issues.apache.org/jira/browse/PHOENIX-2291
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.5.0
> Environment: Centos7 cluster, HBase 1.1, Phoenix 4.5.0
> Reporter: Dan Meany
> Priority: Minor
>
> Intermittently get error below when joining two tables (~10k rows each).
> May be load-related.
> java.lang.RuntimeException: org.apache.phoenix.exception.PhoenixIOException:
> org.apache.phoenix.exception.PhoenixIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException: Could not find hash cache for
> joinId: �X�w��ZY. The cache might have expired and have been removed.
> at
> org.apache.phoenix.coprocessor.HashJoinRegionScanner.<init>(HashJoinRegionScanner.java:96)
> at
> org.apache.phoenix.coprocessor.ScanRegionObserver.doPostScannerOpen(ScanRegionObserver.java:213)
> at
> org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postScannerOpen(BaseScannerRegionObserver.java:179)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$52.call(RegionCoprocessorHost.java:1316)
> Query plan looks like:
> | CLIENT 40-CHUNK PARALLEL 40-WAY FULL SCAN OVER TABLE1_IDX |
> | SERVER FILTER BY FIRST KEY ONLY |
> | PARALLEL LEFT-JOIN TABLE 0 |
> | CLIENT 40-CHUNK PARALLEL 40-WAY FULL SCAN OVER TABLE2_IDX |
> | AFTER-JOIN SERVER FILTER BY "MP.:ID" IS NULL |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
