Member since
01-19-2017
3627
Posts
608
Kudos Received
361
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
226 | 08-02-2024 08:15 AM | |
3412 | 04-06-2023 12:49 PM | |
764 | 10-26-2022 12:35 PM | |
1506 | 09-27-2022 12:49 PM | |
1770 | 05-27-2022 12:02 AM |
02-02-2016
04:21 PM
You need to grant bigotes an ADMIN role but try the below method first Here are the points: 1. You should change all setting with Ambari. 2. Don't change hive.metastore.uris-setting 3. Manually change hiveserver2-site.xml property of hive.security.authorization.manager <property> <name>hive.security.authorization.enabled</name> <value>true</value> </property> <property> <name>hive.security.authorization.manager</name>
<value>org.apache.hadoop.hive.ql.security.authorization.plugin.sqlstd.SQLStdHiveAuthorizerFactory</value> </property> <property> <name>hive.security.authenticator.manager</name>
<value>org.apache.hadoop.hive.ql.security.SessionStateUserAuthenticator</value> </property> <property> <name>hive.metastore.uris</name> <value>''</value> </property> <property> <name>hive.conf.restricted.list</name>
value>hive.security.authorization.enabled,hive.security.authorization.manager,hive.security.authenticator.manager</value>
</property> 4. Copy hiveserver2-site.xml to /etc/hive/conf.server/ 5. Restart hiveserver2 6. Use only beeline for SQL permissions
... View more
02-02-2016
04:03 PM
Whats the output of these 2 scripts SHOW CURRENT ROLES; SHOW ROLES;
... View more
02-02-2016
03:27 PM
Open source sqoop or Syncsort
... View more
02-02-2016
03:05 PM
1 Kudo
Try increasing the number of mappers by appending --m 5 at the end instead on --m 1
... View more
02-02-2016
02:54 PM
The Oozie coordinator supports a very flexible data dependency–based triggering framework. It is important to note that the concept of data availability–based scheduling is a little more involved than time-based triggering.
Use Oozie bundle which is a collection of Oozie coordinator applications with a directive on when to kick off those coordinators.Bundles can be started, stopped, suspended, and managed as a single entity instead of managing each individual coordinator that it’s composed of. This is a very useful level of abstraction in many large enterprises. These data pipelines can get rather large and complicated, and the ability to manage them as a single entity instead of meddling
with the individual parts brings a lot of operational benefits.
... View more
02-02-2016
02:14 PM
@Kibrom Gebrehiwot Re-install should be the last resort because these are real conditions you will meet so start to diagnose and get the sandbox up and running would be a great feat ! How is you network configuration for the Sandbox? Do backup your /etc/hosts and create a new hosts with the below entry 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.225.60 Sandbox.hortonworks.com Sandbox Set your network to DHCP and restart the sandbox
... View more
02-02-2016
01:22 PM
Did you follow these steps during your setup Postgres for Ambari steps
... View more
02-02-2016
01:18 PM
@Kibrom Gebrehiwot These are some of the steps you should try before reinstalling your server! Disable firewall / iptables on the host Run all the below command like root
Execute the below command on the server to disable the firewall, type the following command as the root user to disable firewall for IPv6:
[root@hiroshima01 ~]# service ip6tables stop [root@hiroshima01 ~]# chkconfig ip6tables off [root@hiroshima01 ~]# service iptables status
IPv4 [root@hiroshima01 etc] # service iptables save [root@hiroshima01 etc] # service iptables stop [root@hiroshima01 etc] # chkconfig iptables off Disable Transparent Huge Pages (THP) Disable it on the host otherwise the Ambari install will fail [root@hiroshima01 ~]# echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled [root@hiroshima01 ~]# echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag To disable or make these changes persistent across reboots I add this to the bottom of my vi /etc/rc.local #disable THP at boot time
if test -f /sys/kernel/mm/redhat_transparent_hugepage/enabled; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled fi if test -f /sys/kernel/mm/redhat_transparent_hugepage/defrag; then
echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag
fi To validate THP is disabled, I run the below three commands, or any variant you choose from here . [root@hiroshima01 ~]# cat /sys/kernel/mm/redhat_transparent_hugepage/defrag #output should be always madvise [never]
[root@hiroshima01 ~]# cat /sys/kernel/mm/redhat_transparent_hugepage/enabled # output should be always madvise [never] Disable SELinux SELinux must be disabled for Ambari to function. To temporarily disable SELinux, run the following command on each host in your cluster: [root@hiroshima01 ~]# setenforce 0 Permanently disabling SELinux so that on system reboot it does not restart edit the SELinux config and set SELINUX to disabled. on each host: root@hiroshima01 ]# vi /etc/selinux/config Add the below lines # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Configure the NTPD services
You must setup the NTPD server on CentOS to successfully implement Ambari follow the below steps to install and start the NTPD server. As the root user. To install ntpdate [root@hiroshima01 ~]# yum install ntp ntpdate Turn on the service: [root@hiroshima01 ~]# chkconfig ntpd on Synchronize the system clock with 0.pool.ntp.org server [root@hiroshima01 bin]# ntpdate pool.ntp.org 2 Jan 21:42:49 ntpdate[5101]: 31.3.135.236 rate limit response from server. 2 Jan 21:43:56 ntpdate[5101]: step time server 212.51.144.44 offset 67.520940 sec Check the NTPD services configure it start at system boot [root@hiroshima01 bin]# chkconfig --list ntpd
ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off Start the NTP server. The following will continuously adjust system time from upstream NTP server. No need to run ntpdate: [root@hiroshima01 ~]# /etc/init.d/ntpd start or [root@hiroshima01 ~]# service ntpd start
... View more
02-02-2016
11:29 AM
1 Kudo
Seems you have a DB connectivity problem ,can you copy and paste a complete output of the Ambari failed to start log ? The connection was closed when Java tried to read from it. This can be caused by:
The PostgreSQL server being restarted The PostgreSQL backend you were connected to being terminated The PostgreSQL backend you were connected to crashing Dodgy network connection Badly behaved stateful firewalls Idle connections timing out of the NAT connection tables of NAT firewall/routers ... and probably more. Check the PostgreSQL server logs to see if there's anything informative there; also consider doing some network tracing with a tool like Wireshark.
... View more
02-02-2016
09:40 AM
OOoops GRANT SELECT ON TABLE logs TO USER bigotes WITH GRANT OPTION;
... View more