accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3261) Image Randomwalk fails if no rows are found
Date Mon, 27 Oct 2014 00:44:33 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-3261.
----------------------------------
    Resolution: Fixed

> Image Randomwalk fails if no rows are found
> -------------------------------------------
>
>                 Key: ACCUMULO-3261
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3261
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.5.2, 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.5.3, 1.6.2, 1.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The ScanMeta node from the Image module is subject to failure when the random UUID it
chooses as the starting row sorts after any rows currently in the table.
> {noformat}
> 26 16:52:29,543 [randomwalk.Framework] ERROR: Error during random walk
> java.lang.Exception: Error running node image.ScanMeta
> 	at org.apache.accumulo.test.randomwalk.Module.visit(Module.java:343)
> 	at org.apache.accumulo.test.randomwalk.Framework.run(Framework.java:63)
> 	at org.apache.accumulo.test.randomwalk.Framework.main(Framework.java:122)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.apache.accumulo.start.Main$1.run(Main.java:141)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: ranges must be non null and contain at
least 1 range
> 	at org.apache.accumulo.core.client.impl.TabletServerBatchReader.setRanges(TabletServerBatchReader.java:91)
> 	at org.apache.accumulo.test.randomwalk.image.ScanMeta.visit(ScanMeta.java:87)
> 	at org.apache.accumulo.test.randomwalk.Module$1.call(Module.java:280)
> 	at org.apache.accumulo.test.randomwalk.Module$1.call(Module.java:275)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at org.apache.accumulo.trace.instrument.TraceRunnable.run(TraceRunnable.java:47)
> 	at org.apache.accumulo.core.util.LoggingRunnable.run(LoggingRunnable.java:34)
> 	... 1 more
> {noformat}
> It's likely that this would only arise if ScanMeta is called very early on in the module
which is very unlikely given the weights in Image.xml but lines up with the log file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message