Member since
07-30-2019
453
Posts
112
Kudos Received
80
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2398 | 04-12-2023 08:58 PM | |
| 4970 | 04-04-2023 11:48 PM | |
| 1592 | 04-02-2023 10:24 PM | |
| 3486 | 07-05-2019 08:38 AM | |
| 3400 | 05-13-2019 06:21 AM |
09-13-2018
09:49 AM
Hi @Michael Bronson , ambari will give you recommendations on the Value to be set. You can set any value as per your Cluster and business logic. Once you saved and restart the Yarn clients the changes will be synced to your yarn-site.xml if you are able to save the configuration after clickin on proceed anyway ambari will save 100 . Please see if this helps you.
... View more
09-13-2018
09:27 AM
2 Kudos
Hi @Thiago de Faria , Currently, ambari supports managing only One cluster and one HDP version. If you would like to upgrade only your spark version I would suggest you to mannually install a seperate spark server referring to this document: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_spark-component-guide/content/install-spark-non-ambari.html As per docs.hortonworks.com the HDP-2.6.5 contains Spark-2.3.0 https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_release-notes/content/comp_versions.html Its not suggested to upgrade only Spark with all your HDP components remaining in HDP-2.6.4 Please accept the answer if this helped you.
... View more
09-11-2018
04:56 PM
Hi @Ray Donovan , Referring to your doc i tried to setup the HDF-3.1 and i am successfully able to see and edit the HDF version as mentioned in the helpdoc. I have attached the image for your referrence : Can you please show me what error are you facing. Are you able to see any error in ambari-server.log
... View more
09-11-2018
02:56 PM
Hi @Alex M,
Referring to your error log it seems your agent registration is failing due to below error message :
("WARNING 2018-09-10 23:55:35,248 shell.py:822 - can not switch user for RUN_COMMAND.
WARNING 2018-09-10 23:55:35,352 shell.py:822 - can not switch user for RUN_COMMAND.
INFO 2018-09-10 23:55:35,456 main.py:311 - Agent not going to die gracefully, going to execute kill -9
WARNING 2018-09-10 23:55:35,456 shell.py:822 - can not switch user for RUN_COMMAND.
Are you installing ambari as non-root user , have you given proper permissions as neccessary ?
Also can you please try to install and register ambari-agent mannually : https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-administration/content/install_the_ambari_agents_manually.html
and proceed using the add-host wizard.
Also i assume your node can do password less SSH to ip-10-40-145-25.ec2.internal which is your ambari-server ip. (even if its same host its required to have publickey added to authorized_keys )
cat id_rsa.pub >> authorized_keys
refer to : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-installation/content/set_up_password-less_ssh.html
Please see if this helps you, please login and accept this answer if it did.
... View more
09-07-2018
04:58 PM
@Fraser Campbell, Glad that it helped you :). Please vote for this article if you liked it.
... View more
09-07-2018
05:47 AM
Hi @Joel Hatcher , Glad that metron is started now. Can you please accept the answer so that it will help other community users to understand the correct answer. and for your Ambari showing wrong Metron status, can you confirm whats status in ambari-server.log , attached ambari-agent gives no data about the status . you can check in ambari-server.log and look out for log's from class ServiceResourceProvider
... View more
09-06-2018
10:43 AM
1 Kudo
Hi @Shobhna Dhami ,
The issue is caused due to the fix in AMBARI-22952.
You can resolve this by :
1) stop ambari-server
2) run command : refer : accept GPL license
ambari-server setup --enable-lzo-under-gpl-license
3) start ambari-server
and try again.
Please let me know if this doesn't worked.
Please accept answer if it did
... View more
09-06-2018
01:09 AM
1 Kudo
Hi @Joel Hatcher, as the exception indicates topology already exists why dont you go kill the topology and try to start it again. the syntax for storm CLI will be storm kill topology-name [-w wait-time-secs]
... View more
09-05-2018
04:05 PM
Hi @Kumar Veerappan, I am not sure about how to answer that without knowing your cluster specifications and artitecture. but willn't automatic failover's help you ? If its ambari alerts that are annoying for you. you can investigate , edit the alerts accordingly (you can edit the Alerts on what percent of CPU the alert to trigger ) or even disable it if not required hope this helps you. Please accept answer if it did.
... View more
09-05-2018
03:33 PM
Hi @Kumar Veerappan , Yeah you can know the rack topology structure of cluster using ambari. You can actually refer to this blog which is more helpfull and explained in detail: https://community.hortonworks.com/articles/43164/rack-awareness-series-2.html Please login and accept answer if you found this answer helpfull
... View more