Member since
04-27-2016
9
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1950 | 06-15-2016 07:23 AM |
06-15-2016
01:23 PM
4 Kudos
There are pros/cons for both. VMs have a negative impact on performance so we would normally go for bare metal. Mapreduce is good in scaling to lots of discs/processes even on a single data node. However there are limits on VERY big nodes ( there are new Apollo servers with 24 drives ) you want to increase the HDFS DataNode memory and you may have issues with very big block reports being sent around. In that case logically splitting a node into multiple smaller VMs might solve these issues. But normally I would say go bare metal.
... View more
06-15-2016
07:23 AM
I found it on RedHat documentation, There is no one right answer to this question.
It depends on your needs and requirements. 😞 /dev/: This is the name of the
directory in which all device files reside. Because partitions reside on hard
disks, and hard disks are devices, the files representing all possible
partitions reside in /dev/ Red Hat Enterprise Linux uses a
naming scheme that is file-based, with file names in the form of /dev/xxyN. Where, xx: The first two letters of the
partition name indicate the type of device on which the partition resides,
usually sd. y: This letter indicates which
device the partition is on. For example, /dev/sda for the first hard disk,
/dev/sdb for the second, and so on. N: The final number denotes the
partition. The first four (primary or extended) partitions are numbered 1
through 4. Logical partitions start at 5. So, for example, /dev/sda3 is the
third primary or extended partition on the first hard disk, and /dev/sdb6 is
the second logical partition on the second hard disk. In Red Hat Enterprise Linux each
partition is used to form part of the storage necessary to support a single set
of files and directories. Mounting a partition makes its storage available
starting at the specified directory (known as a mount point). For example, if partition /dev/sda5 is mounted on /usr/, that would
mean that all files and directories under /usr/ physically reside on /dev/sda5.
So the file /usr/share/doc/FAQ/txt/Linux-FAQ would be stored on /dev/sda5,
while the file /etc/gdm/custom.conf would not. It is also possible that one or
more directories below /usr/ would be mount points for other partitions. For
instance, a partition (say, /dev/sda7) could be mounted on /usr/local/, meaning
that /usr/local/man/whatis would then reside on /dev/sda7 rather than
/dev/sda5. Generally speaking, the
disk spacing for /dev partition depends on number and size of the partitions
(both primary and logical)to be used by operating system. However, there is no
one right answer to this question. It depends on your needs and requirements. Conclusion: Red Hat recommends that, unless you have a reason for
doing otherwise, you should at least create the following partitions: swap,
/boot/, and / (root).
... View more
01-31-2018
02:17 PM
Hello all. How can the edge node be installed to the cluster without hooking up with ambari? What are the Pros and Cons?
... View more
06-15-2016
07:46 AM
The Optimized Row Columnar (ORC) file format provides a highly efficient way to store Hive data. It just like a File to store group of rows called stripes, along with auxiliary information in a file footer. It just a storage format, nothing to do with ORC/Spark.
... View more
09-24-2018
02:53 PM
Request for @Ancil McBarnett (or anyone else who knows): Please flesh out a little on ... "You do not want Derby in your cluster."
... View more