[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233420#comment-14233420
]
David Capwell commented on BIGTOP-1493:
---------------------------------------
[~jayunit100]
"for 2nd (mapred) to pass, we will need to implement
http://tachyon-project.org/Running-Hadoop-MapReduce-on-Tachyon.html in the
puppet recipes."
Currently we use libjars to pass tachyon in, so you don't need to integrate
tachyon jars into hadoop lib paths.
"i dont know why we need to test two mapreduce jobs. is there a reason why you
have two jobs ?"
Mostly for validation. The randomtextwriter verifies that the write path smells
ok, and wordcount is used to verify that the read smells ok as well.
"Looks like you left out tachyon:// from the output in the mr job "
{code}
+ def tachyonMasterAddress = prop('TACHYON_MASTER_ADDRESS');
...
+ def input = "${tachyonMasterAddress}${tachyonTestDir}/input"
+ def output = "${tachyonMasterAddress}${tachyonTestDir}/output"
{code}
I expect that the environment variable TACHYON_MASTER_ADDRESS is something like
'tachyon://localhost:19998'
> Add smoke test for tachyon
> --------------------------
>
> Key: BIGTOP-1493
> URL: https://issues.apache.org/jira/browse/BIGTOP-1493
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Assignee: David Capwell
> Attachments: BIGTOP-1493.1.patch, BIGTOP-1493.2.patch,
> BIGTOP-1493.3.patch, iTest-deps.png
>
>
> Tachyon as an in memory cache will be emerging as a common feature in hadoop
> and spark based clusters.
> Lets create a smoke test under the {{smoke-tests}} which uses the
> {{tachyon:///}} url.
> To get started with the smoke tests, you can
> 1) Run the vagrant recipe under bigtop-deploy/vm/vagrant-puppet . This will
> demonstrate the way you spin up a bigtop based hadoop cluster.
> 2) Now, you can do {{vagrant ssh}} into your cluster, and simply edit the
> smoke tests or install stuff. Re running the smoke-tests.sh file should test
> that your new tests work . At that point, just exit your VM, and commit your
> changes and submit the new patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
