I do not think so. The reason why adding ability to specify list of task ports is that we need to decide ahead of time exactly what ports peon processes are going to use in some containerized environments. So if user specify `druid.indexer.runner.ports`, they shoulde ensure these ports are usable. And it may be illegal to use ports which are not contained in user specified ports. In my use case, it does a illegal thing and may cause potential port conflicts.
[ Full content available at: https://github.com/apache/incubator-druid/pull/6263 ] This message was relayed via gitbox.apache.org for [email protected]
