# Deprecation warnings since the upgrade to 7.4.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 2, 2019, 9:12am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917 "2019-10-02T09:12:31Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Yakir\_Gibraltar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yakir_gibraltar/32/54319_2.png) [@Yakir\_Gibraltar](https://discuss.elastic.co/u/Yakir_Gibraltar)\ **Post date:** [October 2, 2019, 9:12am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/1 "2019-10-02T09:12:31Z")
Hi, since the upgrade from 7.3.2 to 7.4.0, i see many errors of: ```auto [WARN][o.e.d.t.TransportInfo] [es-data001.tab.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. [WARN][o.e.d.h.HttpInfo] [es-data001.tab.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. ``` From startup log i see: ```auto [2019-10-02T08:33:24,555][INFO][o.e.t.TransportService] [es-data001.tab.com] publish_address {es-data001.tab.com/161.14.112.45:9300}, bound_addresses {[::]:9300} ``` **Version:** ```auto elasticsearch-7.4.0-1.x86_64 ``` **yml:** ```auto cluster.name: dba discovery.seed_hosts: - es-data001.tab.com - es-data002.tab.com - es-data003.tab.com network.bind_host: 0.0.0.0 network.host: 0.0.0.0 network.publish_host: es-data001.tab.com node.name: es-data001.tab.com path.data: "/var/lib/elasticsearch/data/dba" path.logs: "/var/log/elasticsearch/dba" xpack.ml.enabled: false xpack.security.enabled: false xpack.watcher.enabled: false ``` Not sure what need to change in order to fix the warnings. Thanks, Yakir. ---
**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 2, 2019, 9:34am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/2 "2019-10-02T09:34:19Z")
> [@Yakir\_Gibraltar](#): > > Not sure what need to change in order to fix the warnings. The warnings tell you this information, although it's perhaps not worded very clearly: `... Use -Des.transport.cname_in_publish_address=true to enforce non-deprecated formatting.` and `... es.http.cname_in_publish_address system property is deprecated ... Remove this property to get rid of this deprecation warning.` So you need to set the `es.transport.cname_in_publish_address` property and stop setting the `es.http.cname_in_publish_address` property. ---
**Author:** ![Yakir\_Gibraltar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yakir_gibraltar/32/54319_2.png) [@Yakir\_Gibraltar](https://discuss.elastic.co/u/Yakir_Gibraltar)\ **Post date:** [October 2, 2019, 10:49am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/3 "2019-10-02T10:49:33Z")
Thanks @DavidTurner, but i don't not see `es.http.cname_in_publish_address` in my conf: Current JVM conf: ```auto -Dfile.encoding=UTF-8 -Dio.netty.noKeySetOptimization=true -Dio.netty.noUnsafe=true -Dio.netty.recycler.maxCapacityPerThread=0 -Djava.awt.headless=true -Djna.nosys=true -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -XX:+AlwaysPreTouch -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -XX:GPGCTargetPeakHeapOccupancyPercent=95 -Xloggc:/var/log/elasticsearch/dba/gc.log -Xms32g -Xmx32g -Xss1m -server -verbose:gc ``` ````auto [root@es-data001 ~]# curl -s "http://localhost:9200/_nodes" | jq ".nodes[].transport.publish_address" "171.18.137.79:9300" "171.18.137.80:9300" "171.18.137.81:9300" [root@es-data001 ~]# curl -s "http://localhost:9200/_nodes" | jq ".nodes[].http.publish_address" "es-data002.taboolasyndication.com/171.18.137.79:9200" "es-data003.taboolasyndication.com/171.18.137.81:9200" "es-data001.taboolasyndication.com/171.18.137.80:9200"``` **yml:** ```cluster.name: dba discovery.seed_hosts: - es-data001.tab.com - es-data002.tab.com - es-data003.tab.com network.bind_host: 0.0.0.0 network.host: 0.0.0.0 network.publish_host: es-data001.tab.com node.name: es-data001.tab.com path.data: "/var/lib/elasticsearch/data/dba" path.logs: "/var/log/elasticsearch/dba" xpack.ml.enabled: false xpack.security.enabled: false xpack.watcher.enabled: false``` Thanks. ```` ---
**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 2, 2019, 11:16am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/4 "2019-10-02T11:16:24Z")
Hmm, yes, I also see this now that I'm setting my publish host like yours. Do you need to set your `network.publish_host` to a host name like that? You normally don't need to set `network.bind_host` or `network.publish_host` at all. ---
**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 2, 2019, 11:30am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/5 "2019-10-02T11:30:40Z")
I think this might be a bug so I opened [https://github.com/elastic/elasticsearch/issues/47436](https://github.com/elastic/elasticsearch/issues/47436). ---
**Author:** ![Yakir\_Gibraltar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yakir_gibraltar/32/54319_2.png) [@Yakir\_Gibraltar](https://discuss.elastic.co/u/Yakir_Gibraltar)\ **Post date:** [October 2, 2019, 11:42am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/6 "2019-10-02T11:42:52Z")
Thanks @DavidTurner for **very fast** response, anyway, I'll try to remove `network.bind_host` and `network.publish_host`. ---
**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\ **Post date:** [October 19, 2019, 11:24am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/7 "2019-10-19T11:24:32Z")
Seen the same now on 7.4 using: ``` network.host: _global_,_local_ ``` EDIT: Appears that this only plays out on the elastic nodes that my kibana instance are pointed to ---
**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 20, 2019, 9:59am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/8 "2019-10-20T09:59:36Z")
Thanks @stefws, I think that is consistent with the issue mentioned above, and a fix will be available in 7.4.1. This other thread has a temporary workaround for 7.4.0 if the warnings are intolerable, but otherwise I'd recommend leaving it alone and upgrading when the fix is released. > [@Transport.publish\_address was printed as \[ip:port\] instead of \[hostname/ip:port\]](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/6): > > 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 17, 2019, 9:59am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/9 "2019-11-17T09:59:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.