Do you see any errors in /var/log/das/das-webapp.log? This log file would be on das-webapp host if possible please attach the file to the thread. ... View more

@Simon Waligo What version of Python you are using (i.e Default Python version for the OS set to?) As of Ambaro 2.7.1, Python 2.7 is supported, ref: https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/bk_ambari-installation/content/mmsr_software_reqs.html Also If you are on 2.7, you can try below command to see if it helps? pip install importlib ... View more

@Gopal Mehakare The exception posted is very generic. Can you attach or check Yarn Application logs for the query run? ... View more

@Anurag Mishra By Default Ambati should take care while starting Atlas service, it runs acl script to provide the access below. if the same is not run you can re-run it. /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --authorizer-properties zookeeper.connect=<ZOOKEEPER_HOSTNAME>:2181 --add --topic ATLAS_HOOK --allow-principal User:* --producer /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --authorizer-properties zookeeper.connect=<ZOOKEEPER_HOSTNAME>:2181 --add --topic ATLAS_HOOK --allow-principal User:atlas --consumer --group atlas /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --authorizer-properties zookeeper.connect=<ZOOKEEPER_HOSTNAME>:2181 --add --topic ATLAS_ENTITIES --allow-principal User:atlas --producer /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --authorizer-properties zookeeper.connect=<ZOOKEEPER_HOSTNAME>:2181 --add --topic ATLAS_ENTITIES --allow-principal User:rangertagsync --consumer --group ranger_entities_consumer ... View more

@Bala Kolla You can go by the article https://community.hortonworks.com/articles/149899/investigating-when-llap-doesnt-start.html Let me know if it helps in narrowing down the problem? ... View more

@Anurag Mishra The problem could possibly because of Kafka topic permissions, You may want to check permissions for Kafka topic ATLAS_HOOK, if you are using ranger please follow below instructions. Create following Kafka policies: topic=ATLAS_HOOK permission=publish, create; group=public permission=consume, create; user=atlas (for non-kerberized environments, set group=public) topic=ATLAS_ENTITIES permission=publish, create; user=atlas (for non-kerberized environments, set group=public) permission=consume, create; group=public Also adding to that if Ranger is not in use then you may want to run below commands as Kafka User to give permissions. /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --add --group * --allow-principal User:* --operation All --authorizer-properties "zookeeper.connect=<ZOOKEEPER_HOST>:2181" /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --add --topic ATLAS_ENTITIES --allow-principal User:* --operation All --authorizer-properties "zookeeper.connect=<ZOOKEEPER_HOST>:2181" /usr/hdp/current/kafka-broker/bin/kafka-acls.sh --add --topic ATLAS_HOOK --allow-principal User:* --operation All --authorizer-properties "zookeeper.connect=<ZOOKEEPER_HOST>:2181" ... View more

@Anurag Mishra You may have another process listening on 9083 and 10000 port, can you check if the is another process listening on it? netstat -tualnp |grep :9083 netstat -tualnp |grep :10000 If you find stale process, you can kill it and try starting service again. ... View more

@Praveen Kumar Can you check Oozie launcher job and get the sqoopmapreduce application id and then check that logs? Or you can attach the log to the thread. ... View more

What exception do you see when running the query? You can check the hive view logs in Ambari Server For Hive View 1.5, you can check /var/log/ambari-server/hive-next-view/hive-view.log For Hive View 1.0: /var/log/ambari-server/ambari-server.log You may also check hiveserver2.log file on Hiveserver2 host while creating a table. ... View more

@Sai Krishna Makineni Somehow the query does not work on Hive 1.2.1, Your query looks good, can you check data format in ts column? I had in below format YYYY-mm-dd HH:MM:SS ... View more

Below query may help you with your use case? select * from test where data>(select FROM_UNIXTIME(UNIX_TIMESTAMP()-86400)) Where data column holds data in timestamp format -> YYYY-mm-dd HH:MM:SS To export using beeline below is command can be used. beeline --outputformat=csv2 -u "JDBC_CONNECT_STRING" -n USERNAME -e "select * from test where data>(select FROM_UNIXTIME(UNIX_TIMESTAMP()-86400))" > /tmp/output.txt OR if you want to exclude headers, you can run beeline --showheader=false --outputformat=csv2 -u "JDBC_CONNECT_STRING" -n USERNAME -e "select * from test where data>(select FROM_UNIXTIME(UNIX_TIMESTAMP()-86400))" > /tmp/output.txt ... View more

@Nikita Jaggi Please let me know if the above helps? ... View more

@Aaron Bossert Please let me know if the above helps? ... View more

It looks Yarn job is running as end-user (Kerberos ticket user). You need to have the user on all the Nodemanager hosts with the same UserID. If you are using AD/LDAP user for Kerberos ticket, you may want to sync users to all the Nodemanagers via SSSD. ... View more

Was the upgrade performed from pre HDP 2.6.3? if so you might want to follow below document to remove duplicates from Ranger db. HDP 2.6.3 introduces unique constraints on a few tables in Ranger DB. Depending upon your environment, Ranger DB may contain duplicate data in these tables prior to the upgrade. To make the upgrade faster, you can manually delete this duplicate data in Ranger DB before performing the upgrade. These steps are optional, but recommended, and only needed for Ranger users. These should be performed after registering and installing the target HDP version but before actually performing the upgrade. Ref: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/upgrade_remove_duplicate_ranger_entries.html ... View more