Varun Vasudev commented on YARN-4451:

bq .Well i guessed that would be the reason but the problem is it overwrites 
without any warning/alert ! So either we need to provide a message that file 
will be overwritten or may be while creating we can keep configurable number of 
logs, say 5.

Can you do a sizing test to see how big the log is?

bq. one more issue is when i tried the REST url "http://<rm http 
address>/ws/v1/cluster/scheduler/logs" using wget, i am getting 
WebApplicationException just wanted to confirm whether i missing something !

What http method are you using - that url only supports POST.

> Some improvements required in Dump scheduler logs
> -------------------------------------------------
>                 Key: YARN-4451
>                 URL: https://issues.apache.org/jira/browse/YARN-4451
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
> Though dumping scheduler logs is very useful option there are few nits in 
> using it
> * for naive or first time user its hard to understand what does {{"Time"}} 
> stand for past or future, IMO it would be slightly better to set the name in 
> the ui as {{"Time Period"}}
> * success message should give where the logs will be found and the file name
> * Need to append the time stamp and the period to the file name, so that its 
> not over ridden
> * From code it seems like it always returns {{"Capacity scheduler logs are 
> being created"}} even though the fair scheduler is set
> * Would having cli option in {{"yarn rmadmin"}}  will also be helpful ? 

This message was sent by Atlassian JIRA

Reply via email to