great, that helps.

I think I understand the problem. HRTR is calling notification on attached 
listeners while still holding the `statusLock` , those listener's reaction ends 
up doing something that needs `statusLock` . Solution would be to call the 
listeners without holding `statusLock` .
which means `TaskRunnerUtils.notifyXX` should be called outside the lock. It 
has the mechanism to run listener in an executor service, but it appears 
`SameThreadExecutor` is used everywhere.
 I will raise a PR sometime soon.

[ Full content available at: 
https://github.com/apache/incubator-druid/issues/6201 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to