accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4467) Random Walk broken because of unmet dependency on commons-math
Date Wed, 21 Sep 2016 20:00:23 GMT


Josh Elser commented on ACCUMULO-4467:

bq. My plan for this was to just fix the immediate problem of RandomWalk not including commons-math,
since AFAICT we hadn't centralized the needed dependencies anywhere

That's fine. My point was that we should consolidate it somewhere (this isn't the first time
we've had problems like this). NBD, if these are separate tasks.

-0 for 1.6 (let it die)
+1 for 1.7
-1 for >=1.8 on the verbatim patch because we start shipping commons-math3 (the patch won't
work, the spirit of the change is still +1).

> Random Walk broken because of unmet dependency on commons-math
> --------------------------------------------------------------
>                 Key: ACCUMULO-4467
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.6.6, 1.7.2
>            Reporter: Dima Spivak
>            Assignee: Sean Busbey
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>         Attachments: ACCUMULO-4467-1.6.v1.patch, ACCUMULO-4467-1.7.v1.patch
> When trying to run the Random Walk with {{LongEach.xml}} module, I hit a failure once
we reach the {{Shard.xml}} step:
> {code}
> 16 19:52:05,146 [randomwalk.Framework] ERROR: Error during random walk
> java.lang.Exception: Error running node Shard.xml
> 	at org.apache.accumulo.test.randomwalk.Module.visit(
> 	at
> 	at org.apache.accumulo.test.randomwalk.Framework.main(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.apache.accumulo.start.Main$
> 	at
> Caused by: java.lang.Exception: Error running node shard.BulkInsert
> 	at org.apache.accumulo.test.randomwalk.Module.visit(
> 	at org.apache.accumulo.test.randomwalk.Module$
> 	at org.apache.accumulo.test.randomwalk.Module$
> 	at
> 	at java.util.concurrent.Executors$
> 	at
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> 	... 1 more
> Caused by: java.lang.Exception: Failed to run map/red verify
> 	at org.apache.accumulo.test.randomwalk.shard.BulkInsert.sort(
> 	at org.apache.accumulo.test.randomwalk.shard.BulkInsert.visit(
> 	... 9 more
> {code}
> Digging into YARN to see why the MR job became unhappy, I see the following:
> {code}
> Error: java.lang.ClassNotFoundException: org.apache.commons.math.stat.descriptive.SummaryStatistics
at$ at$
at Method) at
at java.lang.ClassLoader.loadClass( at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass( at org.apache.accumulo.core.file.rfile.RFile$Writer.<init>(
at org.apache.accumulo.core.file.rfile.RFileOperations.openWriter(
at org.apache.accumulo.core.file.rfile.RFileOperations.openWriter(
at org.apache.accumulo.core.file.DispatchingFileFactory.openWriter(
at org.apache.accumulo.core.client.mapreduce.AccumuloFileOutputFormat$1.write(
at org.apache.accumulo.core.client.mapreduce.AccumuloFileOutputFormat$1.write(
at org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.write(
at org.apache.hadoop.mapreduce.task.TaskInputOutputContextImpl.write(
at org.apache.hadoop.mapreduce.lib.reduce.WrappedReducer$Context.write(
at org.apache.hadoop.mapreduce.Reducer.reduce( at
at org.apache.hadoop.mapred.ReduceTask.runNewReducer( at
at org.apache.hadoop.mapred.YarnChild$ at
Method) at at
at org.apache.hadoop.mapred.YarnChild.main( 
> {code}
> It looks like [this commit|]
introduced a dependency on the {{commons-math}} JAR at runtime (in the RFiles Writer class),
but tests weren't updated to ensure that the same dependency would be put onto the classpath
of MR jobs submitted by Random Walk.
> Props to [~busbey] for helping to figure out the root cause here. On a separate note,
we may want to start running this test before releases, as it appears this regression also
snuck into 1.8.0 and at least one 1.6 release (though, since I don't have any easy way to
test this against non-1.7.2 cluster, I'm limiting the affects versions to what I've confirmed
myself). Ping [~kturner], who might know the simplest way to fix this.

This message was sent by Atlassian JIRA

View raw message