I finally found the issue and resolved it. Note: This is with CDH-5.9.0-1 and installation was executed from Cloudera Manager (fresh installation).   Issue: After adding Sqoop2 service from Cloudera Manager, Sqoop service cannot be started.   Cause: Base on th error in Role log, there is an error that was bugging me the most. "Caused by: org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. " Basically during the installation of Sqoop2 service, the script that does the installation somehow did not create the DB repository (in this case it was PostgreSQL). As you can see the error above it is obvious that was something relating to back-end.   Looking into Sqoop configuration from Clouder Manager, the PostgreSQL database name was sqoop. The DB account was sa and DB Account password was empty. It is very strange.   Solution:   1- You need to access to PostgreSQL to find out whether sqoop account and database are present which they are not. In the case, sa account. And sure enough it was not present. It rings the bell right the way. Changing Embedded PostgreSQL Database Passwords https://www.cloudera.com/documentation/enterprise/5-6-x/topics/cm_ig_embed_pstgrs.html   2- Create account (role) and database for sqoop. Configuring Sqoop 2 to Use PostgreSQLing Embedded https://www.cloudera.com/documentation/enterprise/5-8-x/topics/cdh_ig_sqoop2_configure.html In this case  I created account: sqoop and its password. And database name is sqoop.   3- You need to upgrade sqoop database to make sure that all structures are correct. Use Cloudera Manager to do Sqoop database upgrade. Note: When you creat a new database, there is not structure for Sqoop. By doing the upgrade, the system adjusts all Sqoop tabales needed.   4- Configure new account, database, host and port using Cloudera Manager. Save it. Use Cloudera Manager to configure Sqoop database info. - Sqoop repository DB server with port (Default 7432 for PostgreSQL) Sqoop Repository Database Host: - Sqoop database name Sqoop Repository Database Name: - DB user account Sqoop Repository Database User: - DB password Sqoop Repository Database Password:   5- Start Sqoop service                   ... View more

All,   The resolution to this error is to enable the HDFS HA Enabling. Thank everyone for helping it.   1- You need to pay attention to Failover Controller (FC) already exist on the nodes that you assign to be active and standby for HDFS HA. Basically remove FC from these nodes before doing the HDFS HA Enabling.   2- Have your JournalNodes Edits Directory set up. Usually it is in /var/lib/jn   Once the HDFS HA is enable, you can verify it by doing from Cloudera Manager - HDFS - Instances - Federation and High Availability <- click on it to see the setup   or   -HDFS - Configuration -<Do a search on nameservice> In filed NameNodes Nameservice, you should see all nodes that you assign in HDFS HA.       ... View more