Wangda Tan commented on YARN-3091:

Thanks for jumping in and provide your thoughts. [~gtCarrera], [~sunilg], 
[~ozawa], [~rohithsharma], [~varun_saxena].

I've just updated title of this JIRA a little bit according to suggestions from 
[~gtCarrera]. I think it's better to put improvement and fix together in this 
ticket. Since they share a lot of background works. And +1 to fix bugs prior to 
improvements, but it is possible we can address both of them at some places.

I agree to run Jcarder first to pinpoint problems first, with that, we can get 
some valid inputs. But I'm not sure what's the plan of HADOOP-9213, if it needs 
take more time, we can do some works our side parallelly.

> [Umbrella] Improve and fix locks of RM scheduler
> ------------------------------------------------
>                 Key: YARN-3091
>                 URL: https://issues.apache.org/jira/browse/YARN-3091
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: capacityscheduler, fairscheduler, resourcemanager, 
> scheduler
>            Reporter: Wangda Tan
> In existing YARN RM scheduler, there're some issues of using locks. For 
> example:
> - Many unnecessary synchronized locks, we have seen several cases recently 
> that too frequent access of scheduler makes scheduler hang. Which could be 
> addressed by using read/write lock. Components include scheduler, CS queues, 
> apps
> - Some fields not properly locked (Like clusterResource)
> We can address them together in this ticket.
> (More details see comments below)

This message was sent by Atlassian JIRA

Reply via email to