Services Usage: Difference between revisions
From Lsdf
Jump to navigationJump to search
Line 8: | Line 8: | ||
* The HDFS (Hadoop Filesystem) is accessible both natively (API, 'hadoop' command line tool) and via a '''Hadoop FUSE mount'''. This latter one is NOT production quality and '''should NOT be used for data processing'''. It is provided only for the sake of "user friendliness"! |
* The HDFS (Hadoop Filesystem) is accessible both natively (API, 'hadoop' command line tool) and via a '''Hadoop FUSE mount'''. This latter one is NOT production quality and '''should NOT be used for data processing'''. It is provided only for the sake of "user friendliness"! |
||
* You should strive to use the |
* You '''should strive to use the Hadoop Map-Reduce framework natively''', as this is where the framework excels and where the performance gains will be maximal. |
||
* If you use the framework to call external executables (via the streaming-jar for instance), then you must make sure that the '''external executables do NOT start multiple threads'''. |
Revision as of 15:26, 8 July 2011
Following the usage recommendations means less support requests and better services for all the users.
Storage usage
- Storing small files (say < 1MB) wastes resources unnecessarily and dramatically slows down the transfer speed in any protocol. Please try to use data store formats which result in less big files, instead of keeping thousands of small files around. Files of size 100MB or bigger will give the best results!
Hadoop cluster usage
- The HDFS (Hadoop Filesystem) is accessible both natively (API, 'hadoop' command line tool) and via a Hadoop FUSE mount. This latter one is NOT production quality and should NOT be used for data processing. It is provided only for the sake of "user friendliness"!
- You should strive to use the Hadoop Map-Reduce framework natively, as this is where the framework excels and where the performance gains will be maximal.
- If you use the framework to call external executables (via the streaming-jar for instance), then you must make sure that the external executables do NOT start multiple threads.