Member since
03-16-2017
17
Posts
1
Kudos Received
0
Solutions
08-03-2018
10:46 AM
Thank you Sindhu for your reply. How can you be sure they are using Hive 2.x.. There are 2 hive servers installed both using the same metastore. But all using Hive 1.2.1 as part of the HDP 2.5.0 installation
... View more
04-25-2018
01:39 AM
@Olivia Smith
There can be multiple reasons why this happening. I would say, try to run 5th job and when it gets stuck in ACCEPTED state, please check resource manager logs(grep for application ID of 5th job) to see what is happening. You can check more details on capacity scheduler related configuration here - https://community.hortonworks.com/questions/187933/unable-to-run-the-hadoop-commands-in-sandbox.html?childToView=188916#answer-188916
... View more
04-17-2018
12:25 AM
Hi @Olivia Smith, Ambari has its own Hbase setup, which doesnt need the HBASE service is added to the cluster. when you install the ambari metrics service, you can deploy the hbase (specific to AMS component) in two modes. 1. embedded : which will be single AMS process use the local file system to store its data 2. distribute : uses RS and Master service HDFS file system to store the metrics data. either the case you need to provide the hbase.rootdir and other properties. here are the instructions to run in distribution mode (is recommended when you have large voulme of metrics being collected and store ) https://cwiki.apache.org/confluence/display/AMBARI/AMS+-+distributed+mode on the other node, if you cant get that working, please remove the hbase.rootdir and zookeeper Znode dirctory so that Ambari automatically reconfigure the same (# please note that this will remove your existing metrics ) Hope this helps !!
... View more
10-31-2017
03:09 PM
@Olivia Smith Good to know that the issue is resolved. Yes, you are doing right. After installing to a new node (host) in the cluster we need to edit the ambari-agent.ini file to point to the new Ambari Server FQDN (Hostname) followed by ambari-agent restart. /etc/ambari-agent/conf/ambari-agent.ini . If your issue is resolved then it will be great if you can mark this thread as answered (By Clicking on the "Accept" button) so that it will be helpfulfor other HCC users to quickly browse who are facing the same issue.
... View more
09-28-2018
03:28 PM
The article is very general and doe not provide concrete and specific backup & recovery tools.
... View more
09-19-2017
10:22 PM
This may be a case of configuration defaults not being in sync with recommendations for configuration defaults. During the installation process your cluster will be assigned certain defaults to start. As you move through cluster setup, you'll have the opportunity to change those defaults to the recommended configuration defaults through dialogs that throw warnings and errors onto your screen - it sounds like your administrator may have moved past this step without editing default values to match recommendations. Another possibility is that your administrator has changed configuration settings after cluster setup, but did not change dependencies of those settings based on recommendations. In either case, you should be able to change these fields to their recommended values if they make sense in your environment and pass basic sanity checks.
... View more
03-16-2017
11:06 AM
@osmith I never tried this before but my suggestion would be you can stop the impala service instead of disable imapal shell Cloudera Manager -> Impala -> Action -> Stop
... View more