Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,669
Community Members
 
Community Events
185
Community Groups

bind elasticsearch6.x tansport port i.e 9300(default) on 0.0.0.0

Im not able to access transport port 9300 from outer network, since it is binded locally.

As visible from logs 9300 port listening on localhost and 9200 listening on 0.0.0.0

Faced this issue in ES6.0 version

Logs: ES

[2018-02-20T13:03:41,550][INFO ][o.e.t.TransportService ] [44uN7Fm] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}
[2018-02-20T13:03:41,576][WARN ][o.e.b.BootstrapChecks ] [44uN7Fm] max file descriptors [65535] for elasticsearch process is too low, increase to at least [65536]
[2018-02-20T13:03:41,576][WARN ][o.e.b.BootstrapChecks ] [44uN7Fm] max number of threads [1024] for user [elasticsearch] is too low, increase to at least [4096]
[2018-02-20T13:03:41,576][WARN ][o.e.b.BootstrapChecks ] [44uN7Fm] system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk
[2018-02-20T13:03:44,657][INFO ][o.e.c.s.MasterService ] [44uN7Fm] zen-disco-elected-as-master ([0] nodes joined), reason: new_master {44uN7Fm}{44uN7FmbTcOA8f-Xd0HfJg}{TpO3uskNStmjo7BwXyGX5A}{127.0.0.1}{127.0.0.1:9300}
[2018-02-20T13:03:44,664][INFO ][o.e.c.s.ClusterApplierService] [44uN7Fm] new_master {44uN7Fm}{44uN7FmbTcOA8f-Xd0HfJg}{TpO3uskNStmjo7BwXyGX5A}{127.0.0.1}{127.0.0.1:9300}, reason: apply cluster state (from master [master {44uN7Fm}{44uN7FmbTcOA8f-Xd0HfJg}{TpO3uskNStmjo7BwXyGX5A}{127.0.0.1}{127.0.0.1:9300} committed version [1] source [zen-disco-elected-as-master ([0] nodes joined)]])
[2018-02-20T13:03:44,692][INFO ][o.e.h.n.Netty4HttpServerTransport] [44uN7Fm] publish_address {192.168.70.170:9200}, bound_addresses {[::]:9200}

2 comments

elasticsearch yaml

 

cat /etc/elasticsearch/elasticsearch.yml

cluster.name: XYZ
http.host: 0.0.0.0

Note: network.host doesnt work anymore in ES 6.0.

Tahir Bhat
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2020 • edited

You can see this for the solution

Like code_tester likes this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events