Member since
09-10-2016
82
Posts
6
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6446 | 08-28-2019 11:07 AM | |
5953 | 12-21-2018 05:59 PM | |
3089 | 12-10-2018 05:16 PM | |
2581 | 12-10-2018 01:03 PM | |
1690 | 12-07-2018 08:04 AM |
11-28-2018
08:08 PM
@pradeep kammella : If you found this answer is helpful, please take a moment to login and click the "accept" link on the answer. Thanks!!!
... View more
11-28-2018
11:35 AM
Hi @Shraddha Singh, I encountered same issue during the ambari-agent registration. error: Ambari-agent registration failed with ambari-server due to below issue
EOF occurred in violation of protocol (_ssl.c:618)
ERROR 2018-11-27 13:43:19,511 NetUtil.py:97 - SSLError: Failed to connect. Please check openssl library versions
Resolution: vi /etc/ambari-agent/conf/ambari-agent.ini
force_https_protocol=PROTOCOL_TLSv1_2
vi /etc/python/cert-verification.cfg
[https]
verify=disable
Hope this helps!!!. Thanks
... View more
11-27-2018
07:38 AM
@Selva prabhu : If you found this answer is helpful, please take a moment to login and click the "accept" link on the answer.****
... View more
11-27-2018
06:36 AM
Hi @Shraddha Singh, Follow the below prerequisites for installation 1. Enable NTP $systemctl enable ntpd.service or $service ntpd start
$systemctl status ntpd
2. Setting up Host Name $vim /etc/hosts
<ip_address> <fully.qualified.domain.name> <alias_name>
3. Use the "hostname" command to set the hostname on each host in your cluster. $hostname <fully.qualified.domain.name>
4. $vim /etc/sysconfig/network NETWORKING=yes
HOSTNAME=<fully.qualified.domain.name>
5. Verification $hostname –f
<FQDN>
$hostname –i
<HOST_IP>
6. Configuring iptables $service firewalld stop or $systemclt disable firewalld.service
$service firewalld status
If you want to pre-install the Agents, you can perform a manual agent setup. This involves two steps: Configuring the Ambari Repo Install Ambari Agents 1. Configuring Ambari Repo Log in to your host as root
Add ambari.repo file to /etc/yum.repos.d/
2. Confirm that the repository is configured by checking the repolist $yum repolist 3. Install Ambari agent $yum install ambari-agent 4. Configure the Ambari Agent by editing the ambari-agent.ini file as shown in the following example $vim /etc/ambari-agent/conf/ambari-agent.ini
[server]
hostname=<your.ambari.server.hostname>
url_port=8440
secured_url_port=8441
5. Start agent on all host $ambari-agent start 6. Go to Ambari UI -> Install options -> select Perform manual registration -> Next Hope this helps. Thanks
... View more
11-26-2018
02:45 PM
Hi @Saurabh, oozie jobs -oozie http://oozieurl:11000/oozie/ -len 5 -filter status=RUNNING -jobtype=coord Hope this helps! Thanks
... View more
11-26-2018
12:19 PM
Hi @pradeep kammella, When you perform INSERT OVERWRITE into a table the old data will be moved to trash for some duration. To avoid data moving into trash and free up space immediately just specify auto.purge=true TBLPROPERTIES ("auto.purge"="true") or ("auto.purge"="false") Thanks. Hope it helps!
... View more
11-26-2018
11:26 AM
1 Kudo
Hi @Veera Mundra Error: ERROR manager.SqlManager: Error executing statement: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
MySQL specific CommunicationsException:Communications link failure, then it means that the DB isn't reachable. This can have one or more of the following causes. 1. IP address or hostname in JDBC URL is wrong.
2. Hostname in JDBC URL is not recognized by local DNS server.
3. Port number is missing or wrong in JDBC URL.
4. DB server is down.
5. Firewall issue.
To solve the one or the other, follow the following advice: 1. Verify and test them with ping.
2. Verify it based on my.cnf of MySQL DB.
3. Restart the DB.
4. Verify if mysqld is started without the --skip-networking option.
in the below case, --skip-networking is enabled
$ps ax | grep mysql | head -n 1
/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid --skip-networking
5. Make sure line skip-networking is commented in /etc/my.cnf
6. Disable firewall and/or configure firewall/proxy to allow/forward the port.
7. Look for the bind-address setting in my.cnf on the server, and make sure it's listening on the IP address(or hostname).
7. Replace bind-address = 127.0.0.1 with bind-address = 0.0.0.0 in my.cnf file. my.cnf file is available at /etc/mysql folder
Note: Alternatively (and less securely!) the above step7 will set it up to listen on all addresses - local and remote: bind-address = 0.0.0.0
8. By giving proper permissions: GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'password' WITH GRANT OPTION; FLUSH PRIVILEGES;
Hope it helps!. Thanks
... View more
11-26-2018
09:51 AM
Hi Selva prabhu, Would you increase the value for the below property and try again? oozie-default.xml
<property>
<name>oozie.action.max.output.data</name>
<value>XXXX</value>
</property> Ambari: 1. Navigate to Ambari > Services > Oozie > Configs tab.
2. Expand the Custom oozie-site section.
3. Click the Add Property link.
4. For Key, enter the following: oozie.action.max.output.data
5. For Value, enter the new number of bytes accordingly(Currently the results are exceeding 2048B, try doubling the value)
6. Save configuration.
7. Restart all required components. Hope it helps. Thanks
... View more
11-26-2018
07:26 AM
Hi @Andreas Kühnert Error: ERROR datanode.DataNode (BPServiceActor.java:run(828)) - Initialization failed for Block pool <registering> (Datanode Uuid 18320c3e-647e-40e5-9f46-c559fd6d386f) service to hadoop01.test_nf.simscom.com/182.65.21.112:8020. Exiting. If you add a datanode that already has data in the data dir on local disk, then data there probably has a conflicting cluster id. Solution1:
You should probably delete the local data dir (or move them out of the way) and then format NameNode and start the services.
Note: Note: In this way, you will lose all your data.
Data directory is local file system storage location for each datanode in your cluster. You can find the data dir by searching "dfs.datanode.data.dir" in hdfs-site.xml
Solution2:
1. $cd <dfs.datanode.data.dir>/current
2. $vim VERSION
3. Now you need to change the cluster ID of Datanode to the same as Namenode(you can find the CID in VERSION file in namenode dir(<dfs.namenode.name.dir>/current/VERSION)
4. Change the datanode cluster id from old value to new value (in our case new value is: clusterID=CID-9a023007-6187-4bb0-92ec-cc2063a71ee9).
5. Save and exit
6. Restart the services
Hope it helps. Thanks.
... View more
11-22-2018
05:31 AM
@Akhil S Naik : Thanks for your inputs
... View more