Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Thu, 6 Jul 2017 21:13:00 +0000 (UTC)
From: "Thomas D'Silva (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13081608.1498091501000.188605.1499375580100@Atlassian.JIRA>
In-Reply-To: <JIRA.13081608.1498091501000@Atlassian.JIRA>
References: <JIRA.13081608.1498091501000@Atlassian.JIRA> <JIRA.13081608.1498091501050@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-3969) Delete from table more than 100
 rows fails with IndexOutOfBould
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 06 Jul 2017 21:18:45 -0000


    [ https://issues.apache.org/jira/browse/PHOENIX-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077205#comment-16077205 ] 

Thomas D'Silva commented on PHOENIX-3969:
-----------------------------------------

I think my patch for PHOENIX-3986 should fix this issue. I was running in to this failure for the test I added.

> Delete from table more than 100 rows fails with IndexOutOfBould
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-3969
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3969
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>            Priority: Critical
>         Attachments: PHOENIX-3969.patch
>
>
> That happens because in UngroupedAggregateRegionObserver to check whether we have something to commit we call readyToCommit. We do that for both - data table mutations and local indexes ( indexMutations). In this method we check only rows count from original table, but not the size of mutations list. Since indexMutations is using only for local indexes, in regular cases the list will be empty and when we call commitBatch for empty list it fails with an exception :
> {noformat}
> Error: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.DoNotRetryIOException: GIGANTIC_TABLE,,1498079753609.137788ceb573b20bbbb7cdcaeb6ba489.: Index: 0, Size: 0
> 	at org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:92)
> 	at org.apache.phoenix.util.ServerUtil.throwIOException(ServerUtil.java:58)
> 	at org.apache.phoenix.coprocessor.BaseScannerRegionObserver$RegionScannerHolder.overrideDelegate(BaseScannerRegionObserver.java:240)
> 	at org.apache.phoenix.coprocessor.BaseScannerRegionObserver$RegionScannerHolder.nextRaw(BaseScannerRegionObserver.java:266)
> 	at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2506)
> 	at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32385)
> 	at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
> 	at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> 	at java.util.ArrayList.rangeCheck(ArrayList.java:653)
> 	at java.util.ArrayList.get(ArrayList.java:429)
> 	at org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver.commitBatch(UngroupedAggregateRegionObserver.java:193)
> 	at org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver.doPostScannerOpen(UngroupedAggregateRegionObserver.java:713)
> 	at org.apache.phoenix.coprocessor.BaseScannerRegionObserver$RegionScannerHolder.overrideDelegate(BaseScannerRegionObserver.java:221)
> 	... 7 more (state=08000,code=101)
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)