Ambari showing old hardware specs for agent nodes A customer has HDP 2.5 and Ambari 2.4.0.1. They have a number of slave virtual machines and each one of them initially had 6 CPUs and 32GB of RAM. At some point they changed the hardware specs of the VMs to increase bot CPU and RAM for each node. The problem is that Ambari still shows me the old specs for each node. I don't know how exactly they went about changing the specs, and whether the machines got shutdown in the process or not. My first thought was to restart ambari-agent on each node, but this is a production environment, so I wanted to first ask and get a confirmation that (1) this will indeed refresh the hardware specs seen in Ambari and (2) will not interfere with the various Sqoop jobs that are currently importing data. I can't seem to find a definitive answer in the documentation, so any comments will be appreciated. ... View more

I’m using Sandbox 2.3.2 I have configured Hive with hive.server2.transport.mode=http (because of Knox integration). However, the Hive view in Ambari does not seem to like that. When I leave it at the default out of the box settings (port 10000), I get a connection refused, as expected. But when I change the port to 10001, which is the value of hive.server2.thrift.http.port, I get the following: ERROR [qtp-client-1901] ServiceFormattedException:96 - org.apache.ambari.view.hive.client.HiveClientException: H020 Could not establish connecton to sandbox.hortonworks.com:10001: org.apache.thrift.transport.TTransportException: org.apache.thrift.transport.TTransportException The UI doesn’t give me a way to define the JDBC URL myself, so I can’t set the proper transport mode. So I’m stuck, at least until Hive can support both modes simultaneously (HIVE-5312). If I can, I'd like to avoid setting up a second Hive instance just so that I can get the view working. Any help would be appreciated. ... View more