[
https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488767#comment-16488767
]
Chia-Ping Tsai commented on KAFKA-6941:
---------------------------------------
BTW, the worker id base on the advertisedHost and advertisedPort. However, we
have to build the worker id before doing the port binding so the worker id
always is host:0 if the port is assigned to zero. It may cause some troubles
when invoking many workers in a single JVM. I guess the problem can be resolved
by making worker id configurable (KAFKA-6931)
> when passing port = 0 to worker, the advertisedPort still is 0 rather than a
> random port
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-6941
> URL: https://issues.apache.org/jira/browse/KAFKA-6941
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Major
>
> {code:java}
> public URI advertisedUrl() {
> UriBuilder builder = UriBuilder.fromUri(jettyServer.getURI());
> Integer advertisedPort =
> config.getInt(WorkerConfig.REST_ADVERTISED_PORT_CONFIG);
> if (advertisedPort != null)
> builder.port(advertisedPort);
> else if (serverConnector != null)
> builder.port(serverConnector.getPort()); // should call
> getLocalPort() instead
> log.info("Advertised URI: {}", builder.build());
> return builder.build();
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
