Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
Date: Tue, 11 Apr 2017 02:33:41 +0000 (UTC)
From: "Ian Maxon (JIRA)" <jira@apache.org>
To: notifications@asterixdb.incubator.apache.org
Message-ID: <JIRA.13061800.1491409400000.252767.1491878021702@Atlassian.JIRA>
In-Reply-To: <JIRA.13061800.1491409400000@Atlassian.JIRA>
References: <JIRA.13061800.1491409400000@Atlassian.JIRA> <JIRA.13061800.1491409400304@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ASTERIXDB-1872)
 java.lang.IndexOutOfBoundsException when ingesting data using small memory
 component size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 11 Apr 2017 02:33:46 -0000


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

Ian Maxon commented on ASTERIXDB-1872:
--------------------------------------

The issue was that the LSN was persisted after the filter info, which was 0 length due to getLength() being called on LSMComponentFilterReference before getByteArray() had been called to populate the serialized form of the reference. This form determines the length of the entry in the component metadata. 

> java.lang.IndexOutOfBoundsException when ingesting data using small memory component size
> -----------------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1872
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1872
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: Feeds, Storage
>            Reporter: Chen Luo
>            Assignee: Ian Maxon
>         Attachments: asterix-build-configuration-lsm.xml, ingestTwitterToLocalCluster.sh
>
>
> I was testing LSM merge policies recently, and thus I used small memory component size (storage.memorycomponent.numpages=8, storage.buffercache.pagesize=128kb). However, when ingesting some sample tweets, I kept receiving java.lang.IndexOutOfBoundsException
> {code}
> java.lang.IndexOutOfBoundsException
> 	at java.nio.Buffer.checkIndex(Buffer.java:546)
> 	at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:365)
> 	at org.apache.hyracks.storage.am.common.frames.LIFOMetaDataFrame.isInner(LIFOMetaDataFrame.java:210)
> 	at org.apache.hyracks.storage.am.common.frames.LIFOMetaDataFrame.get(LIFOMetaDataFrame.java:174)
> 	at org.apache.hyracks.storage.am.common.freepage.AppendOnlyLinkedMetadataPageManager.get(AppendOnlyLinkedMetadataPageManager.java:332)
> 	at org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.getTreeIndexLSN(AbstractLSMIOOperationCallback.java:106)
> 	at org.apache.asterix.common.ioopcallbacks.LSMBTreeIOOperationCallback.getComponentLSN(LSMBTreeIOOperationCallback.java:72)
> 	at org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.putLSNIntoMetadata(AbstractLSMIOOperationCallback.java:100)
> 	at org.apache.asterix.common.ioopcallbacks.LSMBTreeIOOperationCallback.afterOperation(LSMBTreeIOOperationCallback.java:47)
> 	at org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:519)
> 	at org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.merge(LSMTreeIndexAccessor.java:112)
> 	at org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTreeMergeOperation.call(LSMBTreeMergeOperation.java:83)
> 	at org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTreeMergeOperation.call(LSMBTreeMergeOperation.java:1)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}
> Is this behavior expected?
> Steps to reproduce
> 1. I started a simple cluster with one CC and one NC using org.apache.asterix.api.common.AsterixHyracksIntegrationUtil, and the configuration file is attached.
> 2. The sample tweets I used is from "https://github.com/ISG-ICS/cloudberry".
> The tweets can be ingested by entering the root directory of the project and typing "./script/ingestTwitterToLocalCluster.sh".
> Note: please use the modified ingestTwitterToLocalCluster.sh attached.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)