[
https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396526#comment-15396526
]
James Taylor commented on PHOENIX-3121:
---------------------------------------
Never mind about executing it serially. With the extra filter, we can't know
when the limit will be reached, so parallel makes sense. If the amount of data
that matches the leading part of the PK is small, it'll only be executed over a
single guidepost anyway.
> Queries with filter and reverse scan failing when limit is a multiple of
> scanner cache size
> -------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3121
> URL: https://issues.apache.org/jira/browse/PHOENIX-3121
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
>
> {code}
> org.apache.hadoop.hbase.UnknownScannerException:
> org.apache.hadoop.hbase.UnknownScannerException: Unknown scanner '644116'.
> This can happen due to any of the following reasons: a) Scanner id given is
> wrong, b) Scanner lease expired because of long wait between consecutive
> client checkins, c) Server may be closing down, d) RegionServer restart
> during upgrade.
> If the issue is due to reason (b), a possible fix would be increasing the
> value of'hbase.client.scanner.timeout.period' configuration.
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3228)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32492)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2208)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:104)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
