wangyang0918 commented on pull request #14692: URL: https://github.com/apache/flink/pull/14692#issuecomment-763683363
> We still create the RestClusterClient when deploying application/session and retrieving. For deploying, it is only used to print the web interface URL. For retrieving, it will be used to talk to the cluster. > Based on above, we will use NO_ADDRESS_RESOLUTION for deploying and TRY_ADDRESS_RESOLUTION for retrieving. Hmm. Maybe I do not make myself clear. The above solution is only for Kubernetes. For Yarn, we indeed have the issue for per-job cluster. Just like you said, on a high level scope, I think we do not have a very good abstraction for all `ClusterDescriptor` now, when we need to create a `RestClusterClient` or not. As well as when and how to print the web interface URL. I will update the PR to the initial solution. ---------------------------------------------------------------- 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: us...@infra.apache.org
