Continuing on series of posts on getting Kerberized Ambari HDP and Isilon up and added the following two post to EMC’s ECN site and Isilon infohub. The infamous ‘401 Authorization Required’ error when starting Kerberized services Hortonworks – Isilon Kerberization First Time Services StartRead more "The infamous ‘401 Authorization Required’ error when starting Kerberized services"
An issue has been seen when a KDC kerberized Hortonworks cluster attempts to start Yarn services or any other services that leverage WebHDFS to start with OneFS 8.0.1. The incorrect generation of the the krb5.conf can leave the file without a READ permission for the services handling WebHDFS calls and authentication cannot occur leading to […]Read more "KDC Kerberized Yarn Services Fail to Start on Isilon OneFS 8.0.1 with Ambari via WebHDFS curl calls"
I just authored this post on EMC’s ECN site, on how to implement Kerberos with HDP with Isilon and AD. https://community.emc.com/community/products/isilon/blog/2016/07/05/kerberizing-ambari-hdp-with-isilon-8001-and-active-directoryRead more "Ambari HDP with Isilon 126.96.36.199 and Active Directory Kerberos Implementation"
Wanted to clear up the implementation of racks with Isilon hdfs and providing rack awareness, using Isilon racks we can provide node location awareness to clients and within-switch datanode connections collocation. This gives you the capability to provide switch aware or top of rack functionality that emulates hdfs local storage implementations, where compute nodes attempt […]Read more "Isilon HDFS and Rack Awareness for DataNode Connections"
You will very likely see this blog focused on implementing big data solutions on EMC Isilon mostly, but occasionally some ScaleIO content will get posted. These are the two products that I spend most of my time working with and implementing currently. But, let’s see what happens…Read more "what this blog will be about"
There appears to be some confusion here; the older Isilon Hadoop docs recommended separate subnet pools for the NameNode (NN) and the DataNodes (DN), this changed recently and now the suggested recommendation is a single subnet pool for NameNode (NN) and DataNodes (DN), the pool should be dynamic to provide clean failover of HDFS services. […]Read more "How many SmartConnect Zones on Isilon for HDFS"