Hello Team,   First thing, are you able to connect to HS2 from any of the edge node? If that is connecting successfully, could you share the same to ensure we form the right connection string here.   Also, could you attach the trace logs here and HS2 logs parallelly at the same as well. ... View more

Thanks @tusharkathpal . Is there a easy way to determine the cause of the failure (catalog server vs resource crunch), given that it happens fairly inconsistent in my case. ... View more

Please find more about the "pros and cons to having hive jobs run as the hive user or the end user" vs. Ranger in our public Cloudera documentation for CDP: Enabling or disabling impersonation (doas) ... View more

To see more on Hive Managed and External tables, please see our public documentation for CDP Hive. ... View more

Thanks. Turned out it's related to incorrect IP.  ... View more

Thanks, it's resolved. Appreciated very much ... View more

@tusharkathpal  okay got it thank you....!   So, here I need to export data from hive/impala into RDBMS table.   Can I export data into MySQL table which have already have some records, previously.. will the export delete the existing data in the MYSQL table?   We are planning to export 1 year data from impala to MySQL table. Can you please help with suggestion.   Thank You ... View more

Hello @saamurai    Thanks for the confirmation.   Cheers! Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

Thanks for your reply @tusharkathpal,   We already addressed this case with our customer to have the load balancer and vIP. but the customers seeing this is a risk points to expose the worker node IPs to the external departments within the same Organization and needs to be handled internally within the same application ~ department.   Is there any alternative scenarios that can be achieve the same approach without exposing the worker node IPs to external system like F5?   ... View more

Try to increase the heap size for nodemanager from Yarn -> Configs and see if that resolves your issue.  If not then probably you will have to do a performance or query tuning.   Please accept this answer if it helps you resolve your issue. ... View more