@Marc Charbonneau The following error indicates that your JDBC URL is not correct. May be the Database Name is missing at the end of the host port of the DB. java.sql.SQLException: No suitable driver found for jdbc:postgresql://REMOVED FOR SECURITY Syntax: jdbc:postgresql://db_host:port/databaseName Example: jdbc:postgresql://erie1.example.com:5432/ambari Example: sudo -u hdfs sqoop import --connect jdbc:postgresql://erie1.example.com:5432/ambari --username ambari --password bigdata --table hosts --hcatalog-database default --hcatalog-table test_sqoop_orc_2 --create-hcatalog-table --hcatalog-storage-stanza "stored as orcfile" -m 1 --driver org.postgresql.Driver . Also please check if the Correct JDBC driver is present in the sqoop client classpath. Example: cp -f /PATH/TO/postgresql-9.3-1101-jdbc4.jar /usr/hdp/current/sqoop-client/lib/ . ... View more

@Sedat Kestepe - The Namenode determines whether a datanode dead or alive by using heartbeats. - Each DataNode sends a Heartbeat message to the NameNode every 3 seconds (default value). - This heartbeat interval is controlled by the "dfs.heartbeat.interval" property defined in hdfs-site.xml file. - If a datanode dies, namenode waits for almost 10 mins before removing it from live nodes. - The time period for determining whether a datanode is dead is calculated as dfs.namenode.heartbeat.recheck-interval + 10 * 1000 * dfs.heartbeat.interval The default values for "dfs.namenode.heartbeat.recheck-interval" is 300000 milliseconds(5 minutes) and dfs.heartbeat.interval is "3 seconds" . Reference: - https://github.com/apache/hadoop/blob/release-2.7.3-RC1/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java#L212 - http://pe-kay.blogspot.com/2016/02/dead-datanode-detection.html . ... View more

@david garcia Moving ambari server involves 4 steps: 1). Stop the old ambari host and then install ambari server to new host. 2). Make the "/etc/ambari-agent/conf/ambari-agent.ini" file change on all the agent hosts to point to new ambari server hostname. 3). Run the ambari-server setup command and then point to the Database instance where your amabri DB is present in the "Advance Database configuration Section". (If using postgres then choose option4 Postgres DB , not the Embedded Postgres DB). OR if you want to move the ambari DB as well to a new host then import the DB dump backup to your new DB host and then during the ambari-server setup command choose new host details. 4). Restart Ambari server and all the ambari agents. . Following link provides more details: https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-reference/content/ch_amb_ref_moving_the_ambari_server.html ... View more

@jorge villa Please try the following link: https://github.com/hortonworks/data-tutorials/blob/archive-hdp-2.5/tutorials/hdp/hdp-2.5/cross-component-lineage-with-apache-atlas-across-apache-sqoop-hive-kafka-storm/assets/crosscomponent_scripts.zip . ... View more

@vijay Rachala We see that you are getting the following error when Ambari is trying to install hadoop from yum repo. It requires "libtirpc-devel" package to be already installed on your host which should come from Operating System repo. Execution of '/usr/bin/yum -d 0 -e 0 -y install hadoop_2_5_6_0_40-client' returned 1. Error: Package: hadoop_2_5_6_0_40-hdfs-2.7.3.2.5.6.0-40.el6.x86_64 (HDP-2.5) Requires: libtirpc-devel You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest - Can you please make sure that the mentioned package "libtirpc-devel" is already installed on your host. You can have a look at the similar post: https://community.hortonworks.com/questions/101877/hdp-2603-install-fails-on-rhel-68-ambari-250-libti.html . ... View more