[
https://issues.apache.org/jira/browse/BIGTOP-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913885#comment-13913885
]
jay vyas commented on BIGTOP-1221:
----------------------------------
https://gist.github.com/jayunit100/9242438 <-- these tests can be used to
highlight that the "copy" action on HDFS Fuse mount is only eventually
consistent. I'll create a JIRA for that. Hope we can commit this patch soon,
its a huge improvement i think to bigtop testing of FUSE mounts, and is also
useable to the broader HCFS community where multi-tenant workloads are of
increasing importance.
For a more distilled reproducer of this, you just run a simple bash script like
this:
{noformat}
#!/bin/bash
for i in {1..50};
do
cp a.txt /tmp/hdfs-test/tmp/root/$i
ls -altrh /tmp/hdfs-test/tmp/root/$i
done
{noformat}
> Expand and updated FUSE tests
> -----------------------------
>
> Key: BIGTOP-1221
> URL: https://issues.apache.org/jira/browse/BIGTOP-1221
> Project: Bigtop
> Issue Type: Bug
> Reporter: jay vyas
> Attachments: BIGTOP-1221.patch
>
>
> The BigTop TestFuseDFS need
> - tests for consistency after individual writes : consistency in FUSE mounts
> is important since there are often associated multitenant workloads. Writes
> should result in immediate recognition of a file.
> - Should use HCFS semantics (That way we can confidently use and maintain
> this for alternative file system implementations).
> - should use logging instead of System.out. That way all the logs can be
> picked up from the same place in case we change the logging framework.
> Logging in trace mode, in any case, will allow us to see everything that the
> ITest shell does, and so might as well use it for other logs.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
