Github user zhangminglei commented on the issue:
https://github.com/apache/flink/pull/3724
@zentol Sorry. I just forgot. I close it right now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3724
@zhangminglei could you close this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enable
Github user zhangminglei commented on the issue:
https://github.com/apache/flink/pull/3724
@StephanEwen Thanks. I might close this PR as there is a refactor to
```YarnFlinkApplicationMasterRunner ``` by combining with
```AbstractYarnFlinkApplicationMasterRunner``` in one class. See :
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3724
I think this should be done differently. The access to the resourceManager
should be under the lock, but not the waiting on the termination future.
Otherwise the lock is held too long.
---
If y
