# Transport.publish\_address was printed as \[ip:port\] instead of \[hostname/ip:port\] **URL:** \ **Category:** Elasticsearch\ **Created:** [October 7, 2019, 11:18am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519 "2019-10-07T11:18:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dsosunov](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dsosunov](https://discuss.elastic.co/u/dsosunov)\ **Post date:** [October 7, 2019, 11:18am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/1 "2019-10-07T11:18:13Z")
We recently deploy a new cluster v7.4 and receiving very strange deprecation warnings. [2019-10-07T07:08:33,504][WARN][o.e.d.t.TransportInfo] [[node-01.example.com](http://node-01.example.com)] transport.publish\_address was printed as [ip:port] instead of [hostname/ip:port]. This format is deprecated and will change to [hostname/ip:port] in a future version. Use -Des.transport.cname\_in\_publish\_address=true to enforce non-deprecated formatting. [2019-10-07T07:08:33,504][WARN][o.e.d.h.HttpInfo] [[node-01.example.com](http://node-01.example.com)] es.http.cname\_in\_publish\_address system property is deprecated and no longer affects http.publish\_address formatting. Remove this property to get rid of this deprecation warning. I started to review which address was actually published: curl "[https://node-02.example.com.com:9200/\_nodes](https://node-02.example.com.com:9200/_nodes)" | jq ".nodes.http.publish\_address" "[node-07.example.com/10.13.0.160:9200](http://node-07.example.com/10.13.0.160:9200)" "[node-06.example.com/10.13.0.151:9200](http://node-06.example.com/10.13.0.151:9200)" "[node-08.example.com/10.13.0.143:9200](http://node-08.example.com/10.13.0.143:9200)" "[node-01.example.com/10.13.0.51:9200](http://node-01.example.com/10.13.0.51:9200)" "[node-05.example.com/10.13.0.141:9200](http://node-05.example.com/10.13.0.141:9200)" "[node-03.example.com/10.13.0.53:9200](http://node-03.example.com/10.13.0.53:9200)" "[node-04.example.com/10.13.0.55:9200](http://node-04.example.com/10.13.0.55:9200)" "[node-02.example.com/10.13.0.52:9200](http://node-02.example.com/10.13.0.52:9200)" As for me, looks good. The second one was: /etc/elasticsearch/jvm.options There are no extra options such as mentioned in warning. The actual command line is: /usr/share/elasticsearch/jdk/bin/java -Xms256m -Xmx256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError -Dio.netty.allocator.type=unpooled -XX:MaxDirectMemorySize=134217728 -Des.path.home=/usr/share/elasticsearch -Des.path.conf=/etc/elasticsearch -Des.distribution.flavor=default -Des.distribution.type=rpm -Des.bundled\_jdk=true -cp /usr/share/elasticsearch/lib/\* org.elasticsearch.bootstrap.Elasticsearch -p /var/run/elasticsearch/elasticsearch.pid --quiet Please help me get rid of this warnings. It's important for us, because we are going to migrate to ESv7 and there are a lot of systems that are using deprecated features, this warning produce a lot of noise. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 7, 2019, 11:28am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/2 "2019-10-07T11:28:36Z")
This is issue [#47436](https://github.com/elastic/elasticsearch/issues/47436) and will be addressed in 7.4.1. ---
**Author:** ![dsosunov](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dsosunov](https://discuss.elastic.co/u/dsosunov)\ **Post date:** [October 7, 2019, 11:33am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/3 "2019-10-07T11:33:51Z")
Thanks, for quick reply But we have two warnings. The issue #47436 it's about es.http.cname\_in\_publish\_address system property is deprecated The second one it's warning about publish address in transport section. curl "[https://node-02.example.com:9200/\_nodes](https://node-02.example.com:9200/_nodes)" | jq ".nodes.transport.publish\_address" "10.13.0.143:9300" "10.13.0.51:9300" "10.13.0.141:9300" "10.13.0.160:9300" "10.13.0.55:9300" "10.13.0.151:9300" "10.13.0.52:9300" "10.13.0.53:9300" and there only IP addresses instead of expected host/ip I've double check configuration and there only two options that some how can affect transport address it's: network.host: [node-02.example.com](http://node-02.example.com) in general all options related to other hosts in the cluster are defined by full name (no CNAME); Is this warning has the same roots or it's can be somehow fixed by other way? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 7, 2019, 11:38am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/4 "2019-10-07T11:38:20Z")
I see, sorry, your message is not well formatted so it's difficult to read both log messages. The one about the transport publish address is correct and instructs you how to resolve it: > [@dsosunov](#): > > `Use -Des.transport.cname_in_publish_address=true to enforce non-deprecated formatting.` ---
**Author:** ![dsosunov](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dsosunov](https://discuss.elastic.co/u/dsosunov)\ **Post date:** [October 7, 2019, 11:57am UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/5 "2019-10-07T11:57:47Z")
@DavidTurner I tried to add this option. The command line become: /usr/share/elasticsearch/jdk/bin/java -Xms256m -Xmx256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError **-Des.transport.cname\_in\_publish\_address=true** -Dio.netty.allocator.type=unpooled -XX:MaxDirectMemorySize=134217728 -Des.path.home=/usr/share/elasticsearch -Des.path.conf=/etc/elasticsearch -Des.distribution.flavor=default -Des.distribution.type=rpm -Des.bundled\_jdk=true -cp /usr/share/elasticsearch/lib/\* org.elasticsearch.bootstrap.Elasticsearch -p /var/run/elasticsearch/elasticsearch.pid --quiet and in logs I see: [2019-10-07T07:55:24,000][WARN][o.e.d.h.HttpInfo] [node-01] es.http.cname\_in\_publish\_address system property is deprecated and no longer affects http.publish\_address formatting. Remove this property to get rid of this deprecation warning. Any workarounds? We are considering to filter such kind of noise in filebeat processors processors: - drop\_event: when: regexp: message: "._es.http.cname\_in\_publish\_address._" ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 7, 2019, 12:04pm UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/6 "2019-10-07T12:04:46Z")
I don't have the code in front of me right now, but if I remember correctly you can set `es.http.cname_in_publish_address` to `false` to suppress this warning until 7.4.1 comes out. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2019, 12:04pm UTC](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/7 "2019-11-04T12:04:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.