Member since
12-12-2013
33
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1648 | 12-03-2017 06:59 PM |
01-05-2018
05:51 PM
@fschneider @pdarvasi In the latest Azure release of cloudbreak - Jan 2018 (sorry don't have version handy), I noticed that my custom DNS server was not being used. Ran into this when I was attempting to enable dynamic DNS updates, domain join and AD authentication via sssd. I had to do the following to get it to work... sed -i s/127.0.0.1/<my DNS server IP>/g /etc/dhcp/dhclient-enter-hooks
sed -i s/"search ${search}"/"search ${search} <my domain> "/g /etc/dhcp/dhclient-enter-hook
... View more
12-14-2017
05:45 AM
1 Kudo
@pdarvasi: (1) Availability set (1 for multiple host groups - masters): Works fine (2) Linux kernel version: is the one in your screenshot - version with patch (3) Kerberos enabled post-provisioning against MIT Kerberos KDC: No issues (4) Kerberos enabled at provision time with new MIT Kerberos KDC: Did not complete in 12 hours..lots of alerts, install pending, and services in invalid state and unable to start, Ambari version could not be determined...will open a separate post
... View more
12-12-2017
04:46 PM
@pdarvasi - testing it today.
... View more
12-06-2017
03:19 PM
@pdarvasi Thanks!
... View more
12-06-2017
03:17 PM
@pdarvasi Will try out and get back to you. Thanks so much!
... View more
12-05-2017
05:14 AM
@pdarvasi We appreciate the speed at which the Cloudbreak team is rolling out changes for Azure. Will report back any issues I run into. Can you please confirm if it includes a fix for this? - Linux kernel version... Thanks
... View more
12-03-2017
06:59 PM
Solution: VM FQDN needs to be shorter than what you get with Azure defaults. This is not a Cloudbreak issue.
... View more
12-03-2017
04:33 PM
Hello, Issue: Around mid-November 2017, ran into an issue with datanodes not coming up, and namenode therefore not coming out of safe node when we kerberized (MIT kerberos KDC) a cluster after we provisioned via Cloudbreak. Reference: https://issues.apache.org/jira/browse/HDFS-12029 https://access.redhat.com/errata/RHBA-2017:1674 https://community.hortonworks.com/articles/109940/after-os-patching-all-the-datanodes-nodes-are-up-b.html Temporary Fix: Hortonworks support was consulted, and they applied a temporary fix: Updated hadoop-env.sh configs in HDFS configs in ambari as follows: Original entry: export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true
${HADOOP_OPTS}" With fix: export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true -Xss1280k ${HADOOP_OPTS}” Restarted services and we were good to go. Strategic solution: Upgrade the underlying OS image to a version that includes a patch. 3.10.0-514.26.2.el7.x86_64
version, per the support engineer Reporting this since an upgrade is being worked, should have done it earlier 😞 @pdarvasi
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak
12-03-2017
04:21 PM
@pdarvasi & @jeff Would be great if we had at least the ARM template out in the marketplace - we currently dont have any offering from Hortonworks to spin up a cluster. Cloudera has Director and an ARM template. Would be great if Hortonworks had a similar model...especially for situations like this.
... View more
12-03-2017
02:35 AM
Just found Cloudbreak missing in the marketplace. Please let me know if this is a Microsoft issue so I can escalate internally. I am in the middle of a PoC with strict timelines and am pretty badly impacted. Your support is much appreciated.
... View more
Labels:
- Labels:
-
Hortonworks Cloudbreak