@ThriftTran    I don't know how you expect any member to help on a subject with no context. The least you could do is provide some logs, screenshots, description of the environment or components etc   ... View more

@ranger  Can you try something like this it  explains how to  connect Hive running on a remote host   ( HiveSever2 )  using commonly used Python package, Pyhive? There are a lot of other Python packages available to connect to remote Hive, but Pyhive package is one of the easy and well-maintained and supported package Here I am assuming you installed already the Pyhive package if not please do that first!   from phive import hive import re,os, time host_name = "localhost" port = 10001 user = "hive" password ="hive" database = "employeeDB" def hiveconnection(host_name, port, user,password, database):           conn = hive.Connection(host=host_name, port=port, username=user, password=password,           database=database, auth='CUSTOM')           cur = conn.cursor()           cur.execute('select * from employees returns limit 5')           result = cur.fetchall()           return result # Call above function output = hiveconnection(host_name, port, user,password, database) print(output)   Before you attempt to connect using Pyhive you should execute the below steps to install the Pyhive package below are the step on an ubuntu machine as Pyhive is dependent on these Modules: Installing gcc sudo apt-get install gcc Install Thrift pip install thrift+ Install SASL pip install sasl Install thrift sasl pip install thrift_sasl   After the above steps have run successfully, you can go ahead and install Pyhive using pip: pip install pyhive should you encounter Pyhive sasl fatal error install the below dependencies. sudo apt-get install libsasl2-dev   Now you can re-test your hive database connection Please let me know         ... View more

@budati  There is a good response by Burgess  that  should work out even for you  CSV with duplicate headers  ... View more

@Harish19  can you include some content? Logs, Screenshots, code or description of actions that lead to the failure. It would be a good idea also to state whether CDH/HDP needless to say the version etc. This will go a long way to help us help you ... View more

@kvinod  Good then close the thread. It's always a good idea to have an external database to host not only the CM/Ambari database but also Oozie, hive, ranger etc in a multitenant architecture and maybe backup the database host periodically to avoid having your backend databases all over the cluster. 20 cents advice ! ... View more

@kvinod  It seems to me you first changed the memory parameters and when you switch user the environmental settings are lost. Could you try these steps below $ sudo -u hbase $ export _JAVA_OPTIONS="-Xmx2048m -Xms2048m" $ hbase hbck   Please adjust the java options according to the memory available on your cluster. ... View more

@kvinod  That error "java.lang.OutOfMemoryError: Java heap space " is as it says memory-related hbase backup [hbck] will acquire by default the heap size of JVM which is usually ~1GB. My config is single cluster 2.6.5 HDP with 12 GB memory You can try setting below option and then try executing hbck adjust it according to the memory available. export _JAVA_OPTIONS="-Xmx2048m -Xms2048m" Make sure your run the backup as user hbase. [hbase@nanyuki ~]$ hbase hbck See attached output [hbase@nanyuki ~]$ hbase hbck 2019-09-12 20:33:35,729 INFO [main] zookeeper.RecoverableZooKeeper: Process identifier=hbase Fsck connecting to ZooKeeper ensemble=nanyuki.socar.de:2181 2019-09-12 20:33:35,770 INFO [main] zookeeper.ZooKeeper: Client environment:zookeeper.version=3.4.6-292--1, built on 05/11/2018 07:15 GMT 2019-09-12 20:33:35,770 INFO [main] zookeeper.ZooKeeper: Client environment:host.name=nanyuki.socar.de 2019-09-12 20:33:35,770 INFO [main] zookeeper.ZooKeeper: Client environment:java.version=1.8.0_112 2019-09-12 20:33:35,770 INFO [main] zookeeper.ZooKeeper: Client environment:java.vendor=Oracle Corporation 2019-09-12 20:33:35,770 INFO [main] zookeeper.ZooKeeper: Client environment:java.home=/usr/jdk64/jdk1.8.0_112/jre 2019-09-12 20:33:35,771 INFO [main] zookeeper.ZooKeeper: Client environment:java.class.path=/usr/hdp/2.6.5.0-292/hbase/conf:/usr/jdk64/jdk1.8.0_112/lib/tools.jar:/usr/hdp/2.6.5.0-292/hbase:/usr/hdp/2.6.5.0-292/hbase/lib/activation-1.1.jar:/usr/hdp/2.6.5.0-292/hbase/lib/aopalliance-1.0.jar:/usr/hdp/2.6.5.0-292/hbase/lib/apacheds-i18n-2.0.0-M15.jar .... ... 2019-09-12 20:33:41,203 INFO [main] util.HBaseFsck: Computing mapping of all store files 2019-09-12 20:33:41,398 INFO [main] util.HBaseFsck: Validating mapping using HDFS state 2019-09-12 20:33:41,398 INFO [main] util.HBaseFsck: Computing mapping of all link files 2019-09-12 20:33:41,503 INFO [main] util.HBaseFsck: Validating mapping using HDFS state 2019-09-12 20:33:42,148 INFO [main] util.HBaseFsck: Finishing hbck Summary: Table testtable3 is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table hbase:meta is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table hbase:acl is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table ATLAS_ENTITY_AUDIT_EVENTS is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table hbase:backup is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table PDFTable is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table jina is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table hbase:namespace is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table PDFTable:DOCID001 is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 Table atlas_titan is okay. Number of regions: 1 Deployed on: nanyuki.socar.de,16020,1568312911672 0 inconsistencies detected. Status: OK 2019-09-12 20:33:42,153 INFO [main] zookeeper.ZooKeeper: Session: 0x16d26b3cb56003c closed 2019-09-12 20:33:42,153 INFO [main] client.ConnectionManager$HConnectionImplementation: Closing master protocol: MasterService 2019-09-12 20:33:42,153 INFO [main] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x16d26b3cb56003d 2019-09-12 20:33:42,155 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down 2019-09-12 20:33:42,157 INFO [main] zookeeper.ZooKeeper: Session: 0x16d26b3cb56003d closed 2019-09-12 20:33:42,157 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down [hbase@nanyuki ~]$ So the backup run smoothly  ... View more

@arunkrish  The is a misconfiguration with your local repo can you share the step you followed. ... View more

@Manoj690  Those are warning you can ignore! If indeed your  HBase indeed is not running, please can you validate your steps against the install steps documented below. Here are the steps to  how install standalone hbase ... View more

@narendra99    Good reference 🙂   https://noirblade.github.io/bigdata/hdfs/namenode/2018/11/12/HDFS_NameNode_memory_calculate.html ... View more

@ilia987    You can set your deployment mode in configuration files or from the command line when submitting a job. Use one of the following options to set the deployment mode: Client deployment mode.                     [The driver runs locally] Cluster deployment mode.                  [The driver runs on the cluster] Standalone Cluster Mode As the name suggests, its a standalone cluster with only spark specific components. It doesn’t have any dependencies on Hadoop components and Spark driver acts as the cluster manager. To launch a Spark application in cluster mode: $ ./bin/spark-submit --class path.to.your.Class --master yarn --deploy-mode cluster [options] <app jar> [app options]   Single node To launch a Spark application in client mode, do the same, but replace cluster with the client. The following shows how you can run spark-shell in client mode: $ ./bin/spark-shell --master yarn --deploy-mode client   Hope that helps   ... View more

@Srm  Can you trim your log I had to scroll the whole page 🙂 ... View more

@Srm  @kwabstian53  From your logs, it clearly shows Ambari can't fire up because it can't access the backend database! Connection to user-172.16.1.30:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Can you run netstat -na on the server? As you are running PostgreSQL databse You have to edit postgresql.conf file in /etc/postgresql/9.3/main directory and change line with 'listen_addresses'. listen_addresses =   '*' Next edit pg_hba.conf file, too. In this file you have set, from which computers you can connect to this server and what method of authentication you can use. host          all         all        172.16.1.30/24         md5 After the editing postgresql.conf and pg_hba.conf you have to restart PostgreSQL server. And retry starting Ambari! ... View more

@Deepesh  @Pervatoju   @andrewsnee0    Talking about challenges expect them in the process of migrating from HDP to CDP. According to info available, the recommended path is from HDP 2.6 to HDP 3.X. currently 3.1.0. The merger made Cloudera take some serious thinking on the choice of what to bundle in the new offering the best of the 2 worlds (HWX & CDH) for example Sentry which was the weakest link was dropped in favor of Ranger!     I have attached a screenshot that will give you a picture of what to expect, I will leave you to appreciate and calculate the efforts for whatever path you will decide to take 🙂 Challenges If you are on HDP just know Ambari is gooooone so you will have to get used to Cloudera Manager,the biggest issue would be security but according to some sources your RBAC policies in Sentry will be migrated to Ranger and mapped correctly. If you have gone through a big version migration you will know that deprecated tool eg Falcon has to be removed before a successful migration so I let you imagine the complexity from HDP to CDP but I still think there will be a good migration tool. Personally I would choose to create a new CDP cluster and copy data across DISTCP. Benefits. CDP is built on world-class industry-tested components as I said best of the 2 worlds so expect some thrust with Kudu/Impala/LLAP and for example simplified backup with BDR, HUE, CM managing many clusters a single glass of pane etc just good stuff coming Use Case Same as HDP 🙂 with more productivity and smart tooling. Integration This will be a challenge to form HDP and CDH users but as industry stand software it should be doable and fun.(LDAP/AD/SSL/TLS/Kerberos/SSO) and some third-party tools like kylo. All these is my personal thoughts and not that of Cloudera. ... View more

@Manoj690  I think this is a permission issue that should be resolved if you followed the below steps Solution: Go to   Ambari  >  Hive  >  CONFIGS  >  ADVANCED  >  Custom hive-site  and add   hive.users.in.admin.role   to the list of comma-separated users who require admin role authorization (such as the user hive). If it doesn't already exist    Restart the stale Hive services for the changes to take effect then retry  ... View more

@CoPen    Edit the Ambari Server agent located in  /etc/ambari-agent/conf/ambari-agent.ini on [master.hadoop.com] to match the below.   [server] hostname=master.hadoop.com [should be the FQDN of your Ambari host] And add the following configuration property to the security section [security] force_https_protocol=PROTOCOL_TLSv1_2 Another solution if your cluster is small install the Ambari Agent on all the hosts manually # apt-get install ambari-agent Configure the Ambari Agent by editing the ambari-agent.ini file as shown in the following: vi /etc/ambari-agent/conf/ambari-agent.ini   [server] hostname=master.hadoop.com [should be the FQDN of your Ambari host] url_port=8440 secured_url_port=8441   Start the agent on every host in your cluster. # ambari-agent start   The agent should successfully register with the Ambari server Server on start and no the Ambari GUI skip and use manual registration. ... View more

@kvinod    You can use MySQL for the component please follow    https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_mysql.html ... View more

@EricL  Sorry about the confusion, the location of /etc/security/keytabs/* is specific to HDP the equivalent of  /var/run/cloudera-scm-agent/process   so try to map  so the command    $ klist -kt  /var/run/cloudera-scm-agent/process/*.keytab   shoule be valid  ... View more

@kal  I have written an article in response to a similar question in HCC before, you have a couple of things to do before this can work! My 2 cents advice you should have first configured the 3 clusters using single KDC, then added a second KDC's on each cluster then proceed to configure Cross_Realm Trust. In the process, you would have gained some knowledge on the implementation having said that you will need KDCs in a Master/Slave configuration to be able to propagate principal and Keytabs between the 2 KDC using krb5_prop this is another chapter on its own. I have already noticed also an error in your krb5.conf in the below part, first you have 3 KDC's which are not replicating.there are specific steps to enable replication between KDC's see the one highlighted in ORANGE the values on the left in [lower case ] should mirror on the right in [upper case] see valid example in BLUE   [domain_realm] .xxxxxxx.net = XXXXXXX.NET xxxxxxx.net = XXXXXXX.NET .xxxxxxx.com = XXXXXXX.NET xxxxxxx.com = XXXXXXX.NET .sys.xxxxxxx.net = SPECTRA.XXXXXXX.NET sys.xxxxxx.net = SPECTRA.xxxxxx.NET --Valid-- [domain_realm] .xxxxxxx.net = XXXXXXX.NET xxxxxxx.net = XXXXXXX.NET .xxxxxxx.com = XXXXXXX.COM xxxxxxx.com = XXXXXXX.COM .spectra.xxxxxxx.net = SPECTRA.XXXXXXX.NET spectra.xxxxxx.net = SPECTRA.xxxxxx.NET You should also configure /etc/hosts file on all the 3 clusters to have IP--HOSTNAME--ALIAS and the files should be copied to all hosts in the cluster if DNS is not resolving. The example below depicts hosts in the 3 different network segments # Cluster 1 192.168.0.1 node1.SPECTRA.XXXXXXX.NET node1 192.168.0.2 node2.SPECTRA.XXXXXXX.NET node2 .... 192.168.0.3 node3.SPECTRA.XXXXXXX.NET node3 # Cluster 2 192.168.1.10 node01.XXXXXXX.NET node01 192.168.1.20 node02.XXXXXXX.NET node02 ......... 192.168.1.30 node03.XXXXXXX.NET node01 # Cluster 3 192.168.2.30 nodex.XXXXXXX.COM nodex 192.168.2.40 nodey.XXXXXXX.COM nodey ......... 192.168.2.50 nodez.XXXXXXX.COM nodez if you could breakdown your steps it would be easier to achieve as I reiterated in the beginning but its doable task. Please let me know ... View more

@kal    whats the output of the below snippet? # klist -kt /etc/security/keytabs/hive.service.keytab Could you also share your krb5.conf? Please garble in the important info but not the format 🙂 ... View more

@kvinod  Is it a production cluster or not? If its the latter is there a reason for not using some other database like Mysql/MariaDB/Oracle? In my implementations I tend to favour these 3 hence I have more hands-on in your case you could try out MariaDB/Mysql as they are open source  ... View more

@irfangk1  If its an HDP cluster then I assume you are using Ambari for managing the HDF cluster, you will need to first prepare the 2 new hosts see the ​Prepare the EnvironmentCloudera document   Then add the hosts to the cluster see Add host to cluster Thereafter add HDF to these 2 new nodes it follows the same procedure as adding HDF Services on an existing HDP Cluster hTH ... View more

@irfangk1  It would be good to clarify whether its a CDH or HDP cluster managed by Ambari or not and any relevant information.     ... View more

@Manoj690  Since the hbase meta  is corrupt, I think this is the procedure to resolve that issue How to fix corrupted files for an HBase table   ... View more

@Manoj690    I think you are missing the MySQL database port  3306 !  the DB listener process runs on that port.  without the port, sqoop won't know how to connect. Can you try  sqoop import --connect jdbc:mysql://hostname:3306/ambari1 --username ambari1 --password xxxxx --table emp -m 1   From the Ambari UI you should validate the default port 3306 is configured  and the connection is working or  CLI HTH       ... View more

@kvinod  For sure you have a double entry in your db.mgmt.properties  one simple way is to split the files as I have done below  [------]    Create a back of the current file cp /etc/cloudera-scm-server/db.mgmt.properties  /etc/cloudera-scm-server/db.mgmt.properties.ORIG Then override the db.mgmt.properties with first the  ORANGE if nothing works then the BLUE   $ sudo vi /etc/cloudera-scm-server/db.mgmt.properties # The source of truth for these settings # is the Cloudera Manager databases and # changes made here will not be reflected # there automatically. # com.cloudera.cmf.ACTIVITYMONITOR.db.type=postgresql com.cloudera.cmf.ACTIVITYMONITOR.db.host=hostname:7432 com.cloudera.cmf.ACTIVITYMONITOR.db.name=amon com.cloudera.cmf.ACTIVITYMONITOR.db.user=amon com.cloudera.cmf.ACTIVITYMONITOR.db.password=4WB4R5yxnp com.cloudera.cmf.REPORTSMANAGER.db.type=postgresql com.cloudera.cmf.REPORTSMANAGER.db.host=hostname:7432 com.cloudera.cmf.REPORTSMANAGER.db.name=rman com.cloudera.cmf.REPORTSMANAGER.db.user=rman com.cloudera.cmf.REPORTSMANAGER.db.password=WceGeruLNG com.cloudera.cmf.NAVIGATOR.db.type=postgresql com.cloudera.cmf.NAVIGATOR.db.host=hostname:7432 com.cloudera.cmf.NAVIGATOR.db.name=nav com.cloudera.cmf.NAVIGATOR.db.user=nav com.cloudera.cmf.NAVIGATOR.db.password=D2tjw5xjoE com.cloudera.cmf.NAVIGATORMETASERVER.db.type=postgresql com.cloudera.cmf.NAVIGATORMETASERVER.db.host=hostname:7432 com.cloudera.cmf.NAVIGATORMETASERVER.db.name=navms com.cloudera.cmf.NAVIGATORMETASERVER.db.user=navms com.cloudera.cmf.NAVIGATORMETASERVER.db.password=elJRINTAth [--------------------------separator-----------------------------] # The source of truth for these settings # is the Cloudera Manager databases and # changes made here will not be reflected # there automatically. # com.cloudera.cmf.ACTIVITYMONITOR.db.type=postgresql com.cloudera.cmf.ACTIVITYMONITOR.db.host=hostname:7432 com.cloudera.cmf.ACTIVITYMONITOR.db.name=amon com.cloudera.cmf.ACTIVITYMONITOR.db.user=amon com.cloudera.cmf.ACTIVITYMONITOR.db.password=O31A60K5SN com.cloudera.cmf.REPORTSMANAGER.db.type=postgresql com.cloudera.cmf.REPORTSMANAGER.db.host=hostname:7432 com.cloudera.cmf.REPORTSMANAGER.db.name=rman com.cloudera.cmf.REPORTSMANAGER.db.user=rman com.cloudera.cmf.REPORTSMANAGER.db.password=BPPShP0O9k com.cloudera.cmf.NAVIGATOR.db.type=postgresql com.cloudera.cmf.NAVIGATOR.db.host=hostname:7432 com.cloudera.cmf.NAVIGATOR.db.name=nav com.cloudera.cmf.NAVIGATOR.db.user=nav com.cloudera.cmf.NAVIGATOR.db.password=QHYL7zUSQe com.cloudera.cmf.NAVIGATORMETASERVER.db.type=postgresql com.cloudera.cmf.NAVIGATORMETASERVER.db.host=hostname:7432 com.cloudera.cmf.NAVIGATORMETASERVER.db.name=navms com.cloudera.cmf.NAVIGATORMETASERVER.db.user=navms com.cloudera.cmf.NAVIGATORMETASERVER.db.password=elJRINTAth   After testing the 2 options depending on success or failure then we could get another option. Make sure you have also followed these steps link.  https://www.cloudera.com/documentation/enterprise/5-14-x/topics/cm_ig_extrnl_pstgrs.html#cmig_topic_5_6_1 Please revert      ... View more

@kvinod  In such a case, you should attach the logs because that's the only source we can use to investigate and get tips of maybe what happened. How long have you cluster been running before going down? Did you ever purge the CMS database?   On large deployments, it's a good strategy to put the monitor roles on their own hosts and isolation. Now that you have deleted the CMS hence lost the data therein you can safely create a new backend database and point the new config to that instance. DB's to recreate Reports Manager  Activity Monitor Please revert   ... View more