thanks i see that in my repo file now.  musta pasted from the wrong one.    again many thanks! ... View more

Please review the support matrix: https://community.emc.com/docs/DOC-37101 Then review the Install guides: some of the services traditionally assigned to Namenode/DataNode are not required for Isilon. All information can be found at https://community.emc.com/docs/DOC-39529 ... View more

For the Isilon metrics in Grafana its actually better to monitor them using the isilon statisics API... I write this up in a blog. https://community.emc.com/people/NickyRuggs/blog/2017/06/17/isilon-telemetry-for-the-hadoop-admin ... View more

Good question, better handled in this WP: https://www.emc.com/collateral/hardware/white-papers/h10588-isilon-data-availability-protection-wp.pdf Look at page 9 to get started.... ... View more

128KB stripes ... View more

Compute is done by servers (physical or virtual) the data is sent to these servers over 10/40 gig networks. Refer to this doc: https://support.emc.com/docu84640_Isilon-OneFS-Enterprise-Features-for-Hadoop.pdf?language=en_US ... View more

isilon moves the network IP of the failed connection to a different NIC in the pool. Node failure is handled the same way on the network portion and the data is striped across the other nodes and they will recreate lost stripes using parity stripes. ... View more

SyncIQ is the site-to-site replication for backup/DR. This is the preferred method for backup and DR. if you are thinking of the 3x copies used in local replication for traditional DAS clusters, it is not necessary on isilon. OneFS protects the files in the background using Forward Error Correction. ... View more

Well this is complex because its a NAS migration that needs to maintain user and group information between the two platforms. If you are using AD or LDAP for Hadoop access on the source side it will be greatly simplified, because you can add Isilon to that same authentication provider. As a first step determine how users are going to be mapped between the two systems. In all cases you need to provide UID/GID parity between the two systems. Isilon has many options there that can help so investigate what is going to work for your environment. Next look at your network and take care to provide a physical network topology that will give the best b/w between the servers and Isilon. After you have these pieces in place configure you Access zone and HDFS setting on isilon to correspond to your design. There are scripts available to help creation of users and directories at https://github.com/Isilon/isilon_hadoop_tools these are useful for new installs and putting users in Isilons "Local Provider" so if your case differs from that manual creation should be used... Test using simple hdfs command: hdfs dfs -touchz hdfs://<isilon_access_zone_fqdn>:8020/user/<username>test.file and check its creation: hdfs dfs -ls hdfs://<isilon_access_zone_fqdn>:8020/user/<username>test.file Test it for several users to make sure. Once this is working to your satisfaction leverage the DistCp utility to copy the files using the Isilon URI as the destination. i.e. hdfs://<isilon_access_zone_fqdn>:8020/ then over the course of several days do incrementals to keep the two systems in sync, then pick a day and do the cutover. Since you can run several instances of Hadoop against the same isilon cluster, I would recommend creating a test Access zone and using a few VMs validate that file permissions and ownership are as expected. This is really the hardest piece because Isilon does strict authentication and Hadoop basically does minimal. Always feel free to reach out to Dell/EMC directly for Professional Services for assistance. ... View more

Isilon uses it own OneFS filesystem to read and write files. The write process follows a certain flow: •First, the Client sends file data as a write, which is received by the write coalescer on the client-connected node. •Then, the node breaks the file in up to 128 KB stripe units and a write plan determines how to aggregate the data stripe units and calculates protection stripe units. •Finally, stripe units are sent to participant nodes over the InfiniBand network to distribute the stripe and a write occur on each node. ... View more

So I have done this before and it is not a stable configuration. I put this together for the Hortoworks SE's https://drive.google.com/open?id=0B-ScwmBGk6GGSjNUeDZnTkc4ekk This is a one node Isilon cluster and a one node Hortonworks installation. All you need to do is configure your networking to use the IPs as configured. (see README) ... View more

Use this installation guide http://www.emc.com/collateral/TechnicalDocument/docu71396.pdf ... View more

Ok that is a hard problem, there are permissions and user accoutns that need to match and since they are already set up its a manunal process for you to match them up. Its easier to install a fresh centosVM and add Isilon to it as a new install. Is this a vitual Isilon node as well or a real cluster? ... View more

I need a bit more information, are you trying to add Isilon to an HWX sandbox VM? or have you already run the cluster create wizard? ... View more

Still having this problem.... Installed from scratch a third time same exact issue. Did minimal installs before and full on install this time.... same issue Can you tell me what component the repository version is looking at? ... View more

also tried with 2.4 stack .... same result. Seems like an ambari-server issue. ... View more

I have the same issue, cant get past it any way.. nothing in the logs, tried multiple browsers, added RAM.... still nothing. ... View more

@hrongali As a rule of thumb CPU usage on Isilon is dictated by the write workload. This is mainly to do the FEC and striping calculations. There are of course exceptions to this rule but it is a good rule to use in these environments. The namenode service is relatively light weight and never gets in the way. The majority of the network traffic is datanode traffic between the compute nodes and Isilon. ... View more