Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70858F774 for ; Fri, 29 Mar 2013 22:07:17 +0000 (UTC) Received: (qmail 34707 invoked by uid 500); 29 Mar 2013 22:07:17 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 34660 invoked by uid 500); 29 Mar 2013 22:07:17 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 34564 invoked by uid 99); 29 Mar 2013 22:07:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 22:07:17 +0000 Date: Fri, 29 Mar 2013 22:07:17 +0000 (UTC) From: "Billie Rinaldi (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1227) simple.largeRow.LargeRowTest FAILED due to out of range exception MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617772#comment-13617772 ] Billie Rinaldi commented on ACCUMULO-1227: ------------------------------------------ I don't think this is a timing issue, it seems to be a logic issue with the test. It creates a new table with no splits and writes 100 entries each with a row of size 131,072 (and one- or two-byte values). So there are 13,107,390 bytes of data. It changes the split threshold to 2,621,440, then waits 10 seconds, and then checks that there are between 1 and 9 splits on the table. When I recreate this process, the table's single file has size 32,618,617 bytes before splitting, and changing the split threshold eventually results in 16 tablets. 16 tablets is what I would expect based on the file size. I'm not sure what the test is trying to do. It should pass if we make it check that there are between 1 and 16 tablets instead of 1 and 9, but I'm not sure why we're verifying that. > simple.largeRow.LargeRowTest FAILED due to out of range exception > ----------------------------------------------------------------- > > Key: ACCUMULO-1227 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1227 > Project: Accumulo > Issue Type: Bug > Components: test > Affects Versions: 1.4.2, 1.4.3 > Environment: Hortonworks Data Platform 1.1.2 > Reporter: Cheng Xu > Assignee: John Vines > > 4:18:26 runTest (simple.largeRow.LargeRowTest) ............................. DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.test.functional.FunctionalTest -m localhost -u root -p secret -i ip-10-151-77-24-32355 org.apache.accumulo.server.test.functional.LargeRowTest getConfig > DEBUG:test.auto: > { 'tserver.compaction.major.delay':'1', } > DEBUG:test.auto: > INFO:test.auto:killing accumulo processes everywhere > DEBUG:test.auto:localhost: /usr/lib/accumulo/test/system/auto/pkill.sh 9 2000 ip-10-151-77-24-32355.*org.apache.accumulo.start > DEBUG:test.auto:localhost: hadoop fs -rmr /user/root/accumulo-ip-10-151-77-24-32355 > INFO:test.auto:Error output from command: rmr: cannot remove /user/root/accumulo-ip-10-151-77-24-32355: No such file or directory. > DEBUG:test.auto:Exit code: 255 > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo init --clear-instance-name > DEBUG:test.auto:Output from command: 2013-03-26 14:18:29,914 util.Initialize INFO : Hadoop Filesystem is hdfs://ip-10-151-77-24.ec2.internal:8020 > 2013-03-26 14:18:29,916 util.Initialize INFO : Accumulo data dir is /user/root/accumulo-ip-10-151-77-24-32355 > 2013-03-26 14:18:29,916 util.Initialize INFO : Zookeeper server is localhost:2181 > 2013-03-26 14:18:29,916 util.Initialize INFO : Checking if Zookeeper is available. If this hangs, then you need to make sure zookeeper is running > Instance name : ip-10-151-77-24-32355 > Enter initial password for root: ****** > Confirm initial password for root: ****** > 2013-03-26 14:18:30,377 util.NativeCodeLoader INFO : Loaded the native-hadoop library > 2013-03-26 14:18:30,525 security.ZKAuthenticator INFO : Initialized root user with username: root at the request of user !SYSTEM > DEBUG:test.auto:Exit code: 0 > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo logger > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo tserver > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo monitor > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.master.state.SetGoalState NORMAL > DEBUG:test.auto:Output from command: 2013-03-26 14:18:32,095 server.Accumulo INFO : Attempting to talk to zookeeper > 2013-03-26 14:18:32,471 server.Accumulo INFO : Zookeeper connected and initialized, attemping to talk to HDFS > 2013-03-26 14:18:33,736 server.Accumulo INFO : Connected to HDFS > DEBUG:test.auto:Exit code: 0 > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo master > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.test.functional.FunctionalTest -m localhost -u root -p secret -i ip-10-151-77-24-32355 org.apache.accumulo.server.test.functional.LargeRowTest setup > DEBUG:test.auto: > DEBUG:test.auto: > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.test.functional.FunctionalTest -m localhost -u root -p secret -i ip-10-151-77-24-32355 org.apache.accumulo.server.test.functional.LargeRowTest run > DEBUG:test.auto:Waiting for /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.test.functional.FunctionalTest -m localhost -u root -p secret -i ip-10-151-77-24-32355 org.apache.accumulo.server.test.functional.LargeRowTest run to stop in 120 secs > DEBUG:test.auto:err: Thread "org.apache.accumulo.server.test.functional.FunctionalTest" died null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.accumulo.start.Main$1.run(Main.java:89) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.Exception: # of table splits points out of range, #splits=10 table=lr min=1 max=9 > at org.apache.accumulo.server.test.functional.FunctionalTest.checkSplits(FunctionalTest.java:216) > at org.apache.accumulo.server.test.functional.LargeRowTest.test1(LargeRowTest.java:98) > at org.apache.accumulo.server.test.functional.LargeRowTest.run(LargeRowTest.java:86) > at org.apache.accumulo.server.test.functional.FunctionalTest.main(FunctionalTest.java:312) > ... 6 more > ERROR:test.auto:This looks like a stack trace: Thread "org.apache.accumulo.server.test.functional.FunctionalTest" died null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.accumulo.start.Main$1.run(Main.java:89) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.Exception: # of table splits points out of range, #splits=10 table=lr min=1 max=9 > at org.apache.accumulo.server.test.functional.FunctionalTest.checkSplits(FunctionalTest.java:216) > at org.apache.accumulo.server.test.functional.LargeRowTest.test1(LargeRowTest.java:98) > at org.apache.accumulo.server.test.functional.LargeRowTest.run(LargeRowTest.java:86) > at org.apache.accumulo.server.test.functional.FunctionalTest.main(FunctionalTest.java:312) > ... 6 more > FAIL > ====================================================================== > FAIL: runTest (simple.largeRow.LargeRowTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/accumulo/test/system/auto/JavaTest.py", line 56, in runTest > self.waitForStop(handle, self.maxRuntime) > File "/usr/lib/accumulo/test/system/auto/TestUtils.py", line 383, in waitForStop > self.assert_(self.processResult(out, err, handle.returncode)) > AssertionError > INFO:test.auto:killing accumulo processes everywhere > DEBUG:test.auto:localhost: /usr/lib/accumulo/test/system/auto/pkill.sh 1 2000 ip-10-151-77-24-32355.*org.apache.accumulo.start > DEBUG:test.auto:localhost: hadoop fs -rmr /user/root/accumulo-ip-10-151-77-24-32355 > DEBUG:test.auto:Output from command: Moved to trash: hdfs://ip-10-151-77-24.ec2.internal:8020/user/root/accumulo-ip-10-151-77-24-32355 > DEBUG:test.auto:Exit code: 0 > DEBUG:test.auto:localhost: /usr/lib/accumulo/bin/accumulo org.apache.accumulo.server.util.DeleteZooInstance ip-10-151-77-24-32355 > DEBUG:test.auto:Exit code: 0 > DEBUG:test.auto:localhost: rm -rf /usr/lib/accumulo/walogs/ip-10-151-77-24-32355 > DEBUG:test.auto:Exit code: 0 > DEBUG:test.auto:localhost: rm -rf /usr/lib/accumulo/logs/ip-10-151-77-24-32355 > DEBUG:test.auto:Exit code: 0 > ====================================================================== > FAIL: runTest (simple.largeRow.LargeRowTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/accumulo/test/system/auto/JavaTest.py", line 56, in runTest > self.waitForStop(handle, self.maxRuntime) > File "/usr/lib/accumulo/test/system/auto/TestUtils.py", line 383, in waitForStop > self.assert_(self.processResult(out, err, handle.returncode)) > AssertionError > ---------------------------------------------------------------------- > Ran 1 test in 38.133s > FAILED (failures=1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira