@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

Here is the actual fix (it's actually quite loony):  don't wrap the name of the file in the REGISTER statement with single quotes.  That's it. Catastrophic problems here: 1) Obviously not backwards compatible. 2) If this is a problem, why not just indicate that a) the format is wrong, or b) that a path that started with a single-quote did not yield a valid python file or c) anything understandable instead of getting in the middle of the M/R computation and throwing wacky (mkey?  nullPointer) errors. ... View more

Thanks. I guess it is not for total_io_mb but for "memory and v-core utilization". Disk io should be in yarn logs. I will try seek it. ... View more