You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/04/15 14:33:10 UTC

[GitHub] [flink] tillrohrmann commented on issue #8144: [FLINK-12159]. Enable YarnMiniCluster integration test under non-secure mode

tillrohrmann commented on issue #8144: [FLINK-12159]. Enable YarnMiniCluster integration test under non-secure mode
URL: https://github.com/apache/flink/pull/8144#issuecomment-483276795
 
 
   Thanks for looking into this @zjffdu. I agree with you that setting the port to a fixed value is not ideal for reason 1 and 2. Do you run into one of these problems?
   
   What I don't fully understand is problem 3. If a downstream process sets up a `YarnMiniCluster` it could configure the port differently. Flink would not need to be changed. If using the `YarnTestBase`, then all other applications running on this cluster would need to use the default scheduler port.
   
   Currently, your changes break the existing tests.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services