Services Usage: Difference between revisions

Revision as of 15:11, 8 July 2011

Following the usage recommendations means less support requests and better services for all the users.

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!

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 Haddop Map-Reduce framework natively, as

Revision as of 14:59, 8 July 2011 (view source) JillLundykwjyja (talk \| contribs) (→‎Hadoop cluster usage) ← Older edit		Revision as of 15:11, 8 July 2011 (view source) JillLundykwjyja (talk \| contribs) (→‎Hadoop cluster usage) Newer edit →
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 Haddop Map-Reduce framework natively, as