Ngone51 commented on issue #27849: [SPARK-31081][UI][SQL] Make the display of 
stageId/stageAttemptId/taskId of sql metrics configurable in UI
URL: https://github.com/apache/spark/pull/27849#issuecomment-598507962
 
 
   > This entire ui is for debugging purposes so I don't get your argument with 
that. If a user isn't actively looking to see what went on with their job why 
would they go to this UI at all.
   
   I agree that UI is mostly for debugging purposes. But please also note that 
this is living UI(rather than SHS UI). And living UI may shutdown at any time 
before user figure out the root cause (except those long running applications). 
 So, personally, I aways need to restart and insert `Thread.sleep` when I need 
to debug on living UI in case it shutdown before I figure out the root cause. 
So, I think user could always turn on 
`spark.sql.ui.displayTaskInfoForMaxMetric` when they realize they need to 
restart and debug on living UI.
   
   And if they really want to see those ids at any time, they can just turn it 
on always.
   
   Or if we can have better way to display ids, then we can turn it on by 
default. And here's my previous propose to display ids in case you would like 
it:
   
   <img width="595" alt="ids" 
src="https://user-images.githubusercontent.com/16397174/76581609-f3a75a00-650e-11ea-89de-2edb947fc17d.png";>
    
   
   > I really hope in the future with all the things being reverted that I see 
we copy the original authors and reviewers.
   
   Sorry, this is my bad. I'll take care in the future.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to