--
You received this message because you are subscribed to the Google Groups "Alluxio Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alluxio-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello!
Here is a run from runTests:
-------
oleg@dpipe:~/alluxio-1.2.0$ ./bin/alluxio runTests
2016-09-20 17:50:46,219 INFO type (AbstractClient.java:connect) - Alluxio client (version 1.2.0) is trying to connect with FileSystemMasterClient master @ dpipe.enterprise01.planetos.com/10.2.1.94:19998
2016-09-20 17:50:46,258 INFO type (AbstractClient.java:connect) - Client registered with FileSystemMasterClient master @ dpipe.enterprise01.planetos.com/10.2.1.94:19998
runTest Basic CACHE_PROMOTE MUST_CACHE
2016-09-20 17:50:46,443 INFO type (AbstractClient.java:connect) - Alluxio client (version 1.2.0) is trying to connect with BlockMasterClient master @ dpipe.enterprise01.planetos.com/10.2.1.94:19998
2016-09-20 17:50:46,455 INFO type (AbstractClient.java:connect) - Client registered with BlockMasterClient master @ dpipe.enterprise01.planetos.com/10.2.1.94:19998
2016-09-20 17:50:46,492 INFO type (BlockWorkerClient.java:connectOperation) - Connecting to local worker @ dpipe.enterprise01.planetos.com/10.2.1.94:29998
2016-09-20 17:50:46,558 INFO type (BasicOperations.java:writeFile) - writeFile to file /default_tests_files/Basic_CACHE_PROMOTE_MUST_CACHE took 172 ms.
2016-09-20 17:50:46,639 INFO type (BasicOperations.java:readFile) - readFile file /default_tests_files/Basic_CACHE_PROMOTE_MUST_CACHE took 80 ms.
Passed the test!
runTest BasicNonByteBuffer CACHE_PROMOTE MUST_CACHE
Passed the test!
runTest Basic CACHE_PROMOTE CACHE_THROUGH
2016-09-20 17:50:46,759 ERROR type (CliUtils.java:runExample) - Exception running test: alluxio.examples.BasicOperations@69a10787
java.io.FileNotFoundException: /data/files/default_tests_files/Basic_CACHE_PROMOTE_CACHE_THROUGH.alluxio.0x4857F4040071EBFC.tmp (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
at java.io.FileOutputStream.<init>(FileOutputStream.java:101)
at alluxio.underfs.local.LocalUnderFileSystem.create(LocalUnderFileSystem.java:77)
at alluxio.client.file.FileOutStream.<init>(FileOutStream.java:124)
at alluxio.client.file.BaseFileSystem.createFile(BaseFileSystem.java:102)
at alluxio.examples.BasicOperations.writeFile(BasicOperations.java:85)
at alluxio.examples.BasicOperations.call(BasicOperations.java:72)
at alluxio.examples.BasicOperations.call(BasicOperations.java:42)
at alluxio.cli.CliUtils.runExample(CliUtils.java:51)
at alluxio.cli.TestRunner.runTest(TestRunner.java:148)
at alluxio.cli.TestRunner.runTests(TestRunner.java:121)
at alluxio.cli.TestRunner.main(TestRunner.java:98)
Failed the test!
On Tue, Sep 20, 2016 at 8:31 PM, Yupeng Fu <yup...@alluxio.com> wrote:Hi Oleg,I found many failures in the worker.log. Have you been able to run bin/alluxio runTests successfully?
On Tue, Sep 20, 2016 at 9:53 AM, Oleg Mürk <oleg...@gmail.com> wrote:
Hello,
On Tue, Sep 20, 2016 at 6:42 PM, Yupeng Fu <yup...@alluxio.com> wrote:
Are you able to connect to the remote workers? Also, could you paste the logs from alluxio/logs?
On Tue, Sep 20, 2016 at 8:21 AM, Oleg Mürk <oleg...@gmail.com> wrote:./bin/alluxio fs cat "alluxio://dpipe.enteprise01.planetos.com/rel_0_81x04_indexing/dataset/noaa_gfs_pgrb2_global_0.25degree/reftime/2016-09-15T06-00-00/timevar/time/data.ncml"* works *
As You can see regular "fs cat" works so it must be connecting to the workers.
* hangs *cat logs/fuse.log
The client log was attached to the original email. Please see attachment for server logs.Oleg
The tests failed, so I suspect there're issues with under fs setting.Do you run alluxio master and workers on the machine? And what's your ALLUXIO_UNDERFS_ADDRESS configuration in conf/alluxio-env.sh?
Hello,
On Wed, Sep 21, 2016 at 5:56 PM, Yupeng Fu <yup...@alluxio.com> wrote:* When running "tar c /mount | cat > /dev/null" Network bandwidth monitors shows very high network traffic on fuse client machine in *both* directions. Any ideas what might cause it?Where is the fuse client running? It's unclear to me why there're bi-direction network transfers. Some more information about the network stats will be helpful.
I have a separate machine with Alluxio master and worker. Separate machine runs Alluxio FUSE client. Running "tar c /mnt | cat > /dev/null" on it generates 100MB/sec throughput in both directions between Alluxio master/worker and Alluxio fuse client. How much traffic is generated for one random access in a FUSE file?
Oleg
Interesting. It seems like not an issue in Fuse client, but how the command interacts with the client API triggers the traffic in the other direction.Can you try isolating the issue by not piping the commands but running them individually? For example, I assume find /data.alluxio/files/ -name "file" should only incur one-direction traffic.
Glad you found the problem. I think using a temp file locally will avoid the bidirectional traffic. I suspect the issue was because the temp file is under the mount point, so the command performs write to alluxio.
--