[
https://issues.apache.org/jira/browse/BIGTOP-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214737#comment-14214737
]
Evans Ye commented on BIGTOP-1517:
----------------------------------
The patch is ready now!
I've tested it on virtualbox and docker provisioner, both work fine except
running the smoke-tests on docker.
I got following error during the test:
{code}
:mapreduce:test (Thread[main,5,main]) started.
:mapreduce:test
Executing task ':mapreduce:test' (up-to-date check took 1.006 secs) due to:
No history is available.
ENV VARIABLE: HADOOP_CONF_DIR = /etc/hadoop/conf/
[ant:null] Building jar: /root/.gradle/caches/2.1/workerMain/gradle-worker.jar
Starting process 'Gradle Test Executor 2'. Working directory:
/bigtop-home/bigtop-tests/s moke-tests/mapreduce
Command: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71.x86_64/bin/java -D
java.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
- Dfile.encoding=US-ASCII -Duser.country=US
-Duser.language=en -Duser.variant -ea -cp /root
/.gradle/caches/2.1/workerMain/gradle-worker.jar
jarjar.org.gradle.process.internal.launc
her.GradleWorkerMain 'Gradle Test Executor 2'
Successfully started process 'Gradle Test Executor 2'
Gradle Test Executor 2 started executing tests.
org.apache.bigtop.itest.hadoop.mapreduce.TestHadoopExamples STANDARD_ERROR
log4j:WARN No appenders could be found for logger (java.lang.Object).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
mapreduce:test FAILED
:mapreduce:test (Thread[main,5,main]) completed. Took 11 mins 39.408 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':mapreduce:test'.
> Process 'Gradle Test Executor 2' finished with non-zero exit value 137
* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to
get more log output.
BUILD FAILED
Total time: 14 mins 13.849 secs
FAILURE: Build failed with an exception.
* What went wrong:
Process 'Gradle Compiler Daemon 1' finished with non-zero exit value 137
* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to
get more log output.
{code}
I haven't seen that before, so I cancel the patch and run docker provisioner
again, surprisingly, I got the same error.
The pattern looks like the same as the comment posted by jay in BIGTOP-1524.
So I'm wondering if this is an expected result, [~jayunit100]?
> refactor vagrant provisioners to be configurable by yaml file
> -------------------------------------------------------------
>
> Key: BIGTOP-1517
> URL: https://issues.apache.org/jira/browse/BIGTOP-1517
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1517.1.patch
>
>
> In order to update the configurations of our Bigtop Hadoop
> provisioners(docker-puppet and vagrant-puppet), we need to modify its
> Vagrantfile directly. It would be better to have a yaml file for
> configuration management which consolidate all the things we typically care
> about when provisioning a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
