[
https://issues.apache.org/jira/browse/PHOENIX-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187250#comment-16187250
]
James Taylor commented on PHOENIX-4239:
---------------------------------------
[~samarthjain] - IMHO, it's more of a test issue - we're running the rebuilder
way more frequently than would otherwise be run in these tests. Looks like the
exception is due to a region opening. Perhaps we should retry only in that
case? WDYT, [~rajeshbabu]? How will the online region test typically perform on
a real cluster? Will we get false positives?
{code}
2017-09-30 04:20:49,400 DEBUG
[RpcServer.FifoWFPBQ.priority.handler=1,queue=1,port=41061]
org.apache.hadoop.hbase.ipc.CallRunner(126):
RpcServer.FifoWFPBQ.priority.handler=1,queue=1,port=41061: callId: 4 service:
AdminService methodName: GetRegionInfo size: 96 connection: 67.195.81.136:49226
org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region
T000013.T000015,,1506745239398.8fc67b2271d350dd278b0a1b8e458bd8. is opening on
asf916.gq1.ygridcore.net,41061,1506745136460
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2972)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:1140)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegionInfo(RSRpcServices.java:1424)
at
org.apache.hadoop.hbase.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:22731)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2339)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:188)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:168)
2017-09-30 04:20:49,402 DEBUG [main] org.apache.phoenix.util.MetaDataUtil(550):
Region 8fc67b2271d350dd278b0a1b8e458bd8 isn't online due
to:org.apache.hadoop.hbase.exceptions.RegionOpeningException:
org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region
T000013.T000015,,1506745239398.8fc67b2271d350dd278b0a1b8e458bd8. is opening on
asf916.gq1.ygridcore.net,41061,1506745136460
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2972)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:1140)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegionInfo(RSRpcServices.java:1424)
at
org.apache.hadoop.hbase.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:22731)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2339)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:188)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:168)
{code}
FYI, looks like my change stopped the flapping.
> Fix flapping test in PartialIndexRebuilderIT
> --------------------------------------------
>
> Key: PHOENIX-4239
> URL: https://issues.apache.org/jira/browse/PHOENIX-4239
> Project: Phoenix
> Issue Type: Test
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4239.patch, PHOENIX-4239_v2.patch,
> PHOENIX-4239_v3.patch, PHOENIX-4239_v4.patch, PHOENIX-4239_v5.patch
>
>
> To get more info on this flapper:
> https://www.google.com/url?q=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FPhoenix-master%2F1810%2FtestReport%2Fjunit%2Forg.apache.phoenix.end2end.index%2FPartialIndexRebuilderIT%2FtestIndexWriteFailureLeavingIndexActive%2F&sa=D&sntz=1&usg=AFQjCNEj0LexiK8bm4GzGex9JUvu0DBJag
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
