The Isilon Service

The following versions of Cloudera and Isilon products are supported:

• Cloudera Manager 5.2
• CDH 5.1.3
• Isilon OneFS 7.2.0

Before installing a Cloudera Manager cluster to use Isilon storage, perform the following steps on the Isilon OneFS system. For detailed information on setting up Isilon OneFS for Cloudera Manager, see the Isilon documentation at https://community.emc.com/docs/DOC-39529.

1. Create an Isilon access zone with HDFS support.

   Example:
   /ifs/your-access-zone/hdfs

2. Create two directories that will be used by all CDH services:
   1. Create a tmp directory in the access zone.
      • Create supergroup group and hdfs user.
      • Create a tmp directory and set ownership to hdfs:supergroup, and permissions to 1777.

        Example:
        cd hdfs_root_directory
        isi_run -z zone_id mkdir tmp
        isi_run -z zone_id chown hdfs:supergroup tmp
        isi_run -z zone_id chmod 1777 tmp

   2. Create a user directory in the access zone and set ownership to hdfs:supergroup, and permissions to 755

      Example:
      cd hdfs_root_directory
      isi_run -z zone_id mkdir user
      isi_run -z zone_id chown hdfs:supergroup user
      isi_run -z zone_id chmod 755 user

3. Create the service-specific users, groups, or directories for each CDH service you plan to use. Create the directories under the access zone you have created.
   • ZooKeeper: nothing required.
   • HBase
     • Create hbase group with hbase user.
     • Create the root directory for HBase:

       Example:
       hdfs_root_directory/hbase hbase:hbase 755

   • YARN (MR2)
     • Create mapred group with mapred user.
     • Create history directory for YARN:

       Example:
       hdfs_root_directory/user/history mapred:hadoop 777

     • Create the remote application log directory for YARN:

       Example:
       hdfs_root_directory/tmp/logs mapred:hadoop 775

   • Oozie
     • Create oozie group with oozie user.
     • Create the user directory for Oozie:

       Example:
       hdfs_root_directory/user/oozie oozie:oozie 775

   • Hive
     • Create hive group with hive user.
     • Create the user directory for Hive:

       Example:
       hdfs_root_directory/user/hive hive:hive 775

     • Create the warehouse directory for Hive:

       Example:
       hdfs_root_directory/user/hive/warehouse hive:hive 1777

   • Solr
     • Create solr group with solr user.
     • Create the data directory for Solr:

       Example:
       hdfs_root_directory/solr solr:solr 775
       

   • Sqoop
     • Create sqoop group with sqoop2 user.
     • Create the user directory for Sqoop:

       Example:
       hdfs_root_directory/user/sqoop2 sqoop2:sqoop 775

   • Hue
     • Create hue group with hue user.
     • Create sample group with sample user.
   • Spark
     • Create spark group with spark user.
     • Create the user directory for Spark:

       Example:
       hdfs_root_directory/user/spark spark:spark 751

     • Create application history directory for Spark:

       Example:
       hdfs_root_directory/user/spark/applicationHistory spark:spark 1777

Once the users, groups, and directories are created in Isilon OneFS, you are ready to install Cloudera Manager.

If you choose parcel installation on the Cluster Installation screen, the installation wizard will point to the latest parcels of CDH available. To specify CDH 5.1.3 as an option for parcel installation, click More Options and add the following repository URL to the list of parcel repositories: https://archive.cloudera.com/cdh5/parcels/5.1.3/. The screen will refresh after a few seconds, and you can choose CDH 5.1.3.

On the installation wizard's Cluster Setup page, choose Custom Services, and choose the services you want installed in the cluster. Be sure to choose Isilon among the selected services, do not select the HDFS or Impala services, and do not check Include Cloudera Navigator at the bottom of the Cluster Setup page. Also, on the Role Assignments page, be sure to specify the hosts that will serve as gateway roles for the Isilon service. You can add gateway roles to one, some, or all nodes in the cluster.