The job failed with an OutOfMemoryError (OOME) at the child task attempt level, as indicated by the stacktrace. It was observed that certain mapreduce properties have been set, which may potentially overwrite the hive.tez.container.size property.   SET mapreduce.map.java.opts=-Xmx3686m; SET mapreduce.reduce.java.opts=-Xmx3686m; SET mapred.child.java.opts=-Xmx10g;​   It is recommended to validate the yarn appLogs to confirm if the child task attempts were launched with 80% of the hive.tez.container.size. If not, it is advised to remove the mapreduce configurations and try re-running the job. Before re-running the query, it is suggested to collect statistics for all the source tables. This will assist the optimizer in creating a better execution plan. ... View more

@djill Welcome to the Cloudera Community! To help you get the best possible solution, I have messaged you with next steps. Thanks! ... View more

Hey, in the application logs everything looks fine. Instead of being able to click on the application name like I would normally do when the status is running, I have to go into the application logs and find the gradio app link at the bottom.  When I look at the container logs, the last 3 lines are:   2024-11-13 08:22:14.557 18 INFO JupyterWSGLauncher ngh4jdz5m3ua258n Finish running startup chunks: success. data = {"user":"cdsw"} 2024-11-13 08:22:14.557 18 INFO JupyterWSGLauncher ngh4jdz5m3ua258n Proxying to livelog data = {"user":"cdsw"} 2024-11-13 08:22:14.557 18 INFO JupyterWSGTimeoutHandler ngh4jdz5m3ua258n idleTimeoutInMinutes data = {"idleTimeoutInMinutes":60,"user":"cdsw"}   Suggesting everything is as expected?   Edited: I found the problem. It was how I was defining the port for the application. Instead of using 'os.getenv('CDSW_APP_PORT')'  I was using a manually set one.    Thank you! ... View more