Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2730 | 04-27-2020 03:48 AM | |
| 5288 | 04-26-2020 06:18 PM | |
| 4458 | 04-26-2020 06:05 PM | |
| 3584 | 04-13-2020 08:53 PM | |
| 5384 | 03-31-2020 02:10 AM |
03-09-2018
10:55 AM
@maha Rm You will find "Custom tez-site" inside the "Tez" --> Configs --> Advanced --> "Custom tez-site" The click on "Add Property" link and then add that property "tez.tez-ui.history-url.base" with the appropriate value. .
... View more
03-09-2018
10:14 AM
1 Kudo
@Johan Lund May be the following link give more idea on how to use "no_proxy" at the OS level inside the "~/.profile", "~/.bash_profile", ENV level. Like: no_proxy="127.0.0.1, localhost" . https://community.hortonworks.com/questions/120761/ambari-ldap-sync-ldap-issue-with-proxy-getting-502.html
... View more
03-09-2018
09:55 AM
@maha Rm Can you please login to ambari ui and then navigate to "Tez" --> Configs --> Advanced --> "Advanced tez-site" and then look for a property "tez.tez-ui.history-url.base" And then set the value as following: tez.tez-ui.history-url.base = http://$AMBARI_SERVER_HOST:8080/#/main/view/TEZ/tez_cluster_instance . NOTE: Please replace the "AMBARI_SERVER_HOST" value with the actual FQDN (hostname) of the ambari server here and then save the config changes. Example: tez.tez-ui.history-url.base = http://amb25101.example.com:8080/#/main/view/TEZ/tez_cluster_instance Then restart the services that requires restart for this config change to take effect and then you should be all set to add new services. (assuming ambari server hostname is amnb25101.example.com above should be the URL) .
... View more
03-09-2018
09:34 AM
2 Kudos
@Johan Lund Can you pelase add the "-iv" flag to the curl call. I am suspecting that it may be a Proxy issue. So when you use FQDN then your requests might be passing via some proxy server. # curl -iv -u admin:admin -H "X-Requested-by:ambari" -i -k -X GET https://<FQDN>:8443/api/v1/clusters/<CLUSTERNAME>/services/
AND
# curl -iv -u admin:admin -H "X-Requested-by:ambari" -i -k -X GET https://127.0.0.1:8443/api/v1/clusters/<CLUSTERNAME>/services/ . Looks like your ambari-server host might be having some http proxy settings which is not allowing the "localhost" request to be passed via proxy which is rejecting the request. Please see if you have any -Dhttps.proxyHost=proxy_name
-Dhttps.proxyPort=xxxx configured on your ambari server host like in "~/.bash_profile", "~/.profile" or Or in "~/.bashrc" Please check if you have any OS level setting to define proxy host and Non proxy hosts. like: export http_proxy
export https_proxy Or may be at Host environment level or inside some script like /var/lib/ambari-server/ambari-env.sh https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.5/bk_ambari-administration/content/ch_setting_up_an_internet_proxy_server_for_ambari.html .
... View more
03-09-2018
08:03 AM
@Anurag Mishra I am not aware of any such API which can update only a particular Attribute's("userList") particular value. The only option i see is to get the JSON output from the following call and then edit the JSON and then out back the edited json. Get Policy JSON # curl -u admin:admin -H "Content-Type: application/json" -X GET http://$RANGER:6080/service/public/v2/api/policy/12 -o /tmp/policy_12.json . Now edit the JSON "/tmp/policy_12.json" and add new user in the "userList" section and then run the following curl command to update. Update the JSON using Put # curl -u admin:admin -H "Content-Type: application/json" -X PUT -d @/tmp/policy_12.json http://$RANGER:6080/service/public/v2/api/policy/12 .
... View more
03-09-2018
07:50 AM
Please notice the following section in the JSON payload: "userList":["ambari-qa","hdfs"] .
... View more
03-09-2018
07:46 AM
1 Kudo
@Anurag Mishra Are you talking about Ranger "Update Policy" API calls using (-X PUT operations). Something like described in the following link: https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.6+-+REST+APIs+for+Service+Definition%2C+Service+and+Policy+Management#ApacheRanger0.6-RESTAPIsforServiceDefinition,ServiceandPolicyManagement-UpdatePolicybyid Example: # curl -iv -u admin:admin -H "Content-Type: application/json" -d '{"policyName":"restCreate","resourceName":"*","description":"testing REST","repositoryName":"test_hadoop","repositoryType":"hdfs","isEnabled":true,"isRecursive":true,"isAuditEnabled":true,"permMapList":[{"userList":["ambari-qa","hdfs"],"permList":["Read","Write"]}]}' -X PUT http://$RANGER:6080/service/public/v2/api/policy/12 .
... View more
03-09-2018
07:23 AM
@Vishal Gupta Please try this. Change your Tomcat port to 9090 (instead of 2222) and then try again 9090 is the defauilt Nifi Port , which might not be running on your Sandbox and the port forwarding rules are already setup for port 9090 so you should be fine with this port. Change the tomcat port to 9090 and then restart the tomcat then try accessing the tomcat URL on this port.
... View more
03-09-2018
12:05 AM
@Aymen Rahal The current error is completely different from the one which was mentioned in the original thread so it might confuse the users who hit the same issue described in the Original thread. Encountered IOException running import job: java.io.IOException: No columns to generate for ClassWriter at org.apache.sqoop.orm.ClassWriter.generat . Hence i will request you to please mark this HCC thread as "answered" by clicking on the "Accept" button and then open a new thread with the current error. Thats helps many community users to quickly find one specific error with one specific answer.
... View more
03-08-2018
11:58 PM
@Aymen Rahal Yes 3306 is the default port for MySQL. So better to add it in the URL. # sqoop import --connect jdbc:mysql://hadoop:3306/Testdb --table widgets -m 4 --username root --password CHANGEME --driver com.mysql.jdbc.Driver<br> . Also please check if you are able to login to MySQL using command line or not? # mysql -u root -p .
... View more