[PHOENIX-3121] Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.8.0
• Assignee: Samarth Jain
• Reporter: Samarth Jain
• Created: 27/Jul/16 18:07
• Updated: 11/Aug/16 08:28
• Resolved: 01/Aug/16 19:20

Description

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)

Issue Links

• relates to: PHOENIX-3133 Investigate why offset queries with reverse scan take a long time