[
https://issues.apache.org/jira/browse/BIGTOP-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283424#comment-14283424
]
David Capwell commented on BIGTOP-1572:
---------------------------------------
Sorry [~jayunit100], seems I didn't see this when you first messaged me.
When you do copyFromLocal, it will respect
"tachyon.user.file.writetype.default" which defaults to
WriteType.CACHE_THROUGH. This means that the file will be both in tachyon and
on HDFS.
What in-memory means is that its in tachyon fully. When the blocks of the file
get evicted, then the UI will show that its no longer in-memory.
About taking over, I can help out with vagrant, not sure about the HCFS. Could
you give more details on how bigtop does this today? I belive that gridgain is
the first, so is there anything in place from that or are they in the same boat
as tachyon right now?
> Perfect the automated install, smoke tests, and integration of tachyon-HDFS
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-1572
> URL: https://issues.apache.org/jira/browse/BIGTOP-1572
> Project: Bigtop
> Issue Type: Bug
> Components: deployment, tests
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Fix For: 0.9.0
>
>
> Following BIGTOP-1493, its now super easy to verify perfect integration of
> tachyon on the bigtop distro.
> *but* Im finding that the automated tests fail b/c we dont have the config
> parameters glued into HDFS by puppet on installation... Also it seems that
> the logging isnt good enough (INFO by default instead of DEBUG).
> Lets
> - fix integration into HDFS (preferably in a HCFS compliant way) and
> - make sure tachyon installation works perfectly on {{vagrant up}}
> - confirm that adding tachyon to the smoke
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
