discuss.elastic.co Open in urlscan Pro
2602:fd3f:3:ff02::2f  Public Scan

URL: https://discuss.elastic.co/t/what-are-ports-9200-and-9300-used-for/238578
Submission: On April 25 via api from US — Scanned from DE

Form analysis 1 forms found in the DOM

POST /login

<form id="hidden-login-form" method="post" action="/login" style="display: none;">
  <input name="username" type="text" id="signin_username">
  <input name="password" type="password" id="signin_password">
  <input name="redirect" type="hidden">
  <input type="submit" id="signin-button" value="Log In">
</form>

Text Content

DISCUSS THE ELASTIC STACK


WHAT ARE PORTS 9200 AND 9300 USED FOR?

Meta Elastic Elastic Tips and Common Fixes
elasticsearch

warkolm (Mark Walkom) June 25, 2020, 12:51am #1

[This is an extension on an older thread - Elasticsearch port 9200 or 9300?]

By default, Elasticsearch uses two ports to listen to external TCP traffic;

 * Port 9200 is used for all API calls over HTTP. This includes search and
   aggregations, monitoring and anything else that uses a HTTP request. All
   client libraries will use this port to talk to Elasticsearch
 * Port 9300 is a custom binary protocol used for communications between nodes
   in a cluster. For things like cluster updates, master elections, nodes
   joining/leaving, shard allocation

Historically, port 9300 was also used for connections from client libraries,
however this type of interaction is deprecated across our official clients, and
not supported elsewhere.

You can change the ports that Elasticsearch uses for this, via the http.port and
transport.port settings.

4 Likes

Elasticsearch port 9200 or 9300?
Will es nodes connect with each other in 9200?
 * Home
 * Categories
 * FAQ/Guidelines
 * Terms of Service
 * Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled

Skip to main content
Sign UpLog In
 * 
 * 
 * 
 * 
 * 


NEW IN ELASTIC 8.1

Elastic 8.1 enables our customers and community to further accelerate software
development lifecycles with deeper visibility into both serverless architectures
and CI/CD pipelines. In addition, Elastic 8.1 includes new prebuilt detections,
malicious behavior protections, and data source integrations to help
organizations more efficiently stop advanced adversaries before they are able to
cause harm.

As these new features are best seen in action, it's time to begin (or continue)
your Elastic journey. Elastic 8.1 is available now on Elastic Cloud — the only
hosted Elasticsearch offering to include all of the new features in this latest
release. You can always download a self-managed version of the Elastic Stack for
free.

Learn more with our release blog posts:


RELEASE BLOGS

Elastic Blog


ELASTIC 8.1: ACCELERATE APP DEVELOPMENT AND DEFEND AGAINST NOVEL ATTACKS

With more data source integrations, new prebuilt detections, faster indexing
speeds, reduced data storage requirements, and enhanced ad hoc analytics
capabilities — Elastic 8.1 is here to help the world’s leading organizations
search, solve, and...



Elastic Blog


ELASTICSEARCH, KIBANA, ELASTIC CLOUD 8.1: FASTER INDEXING, LESS DISK STORAGE,...

In 8.1, Elasticsearch and Kibana help you search, solve, and succeed with 20%
faster indexing, a 20% reduction in storage requirements, and new ad-hoc
analytics capabilities. Search smarter with new visualizations, Geohexgrid, and
more, on Elastic...



Elastic Blog


ELASTIC SECURITY 8.1: STOP NOVEL ATTACKS IN THEIR TRACKS

With Elastic Security 8.1, stop novel attacks in their tracks. Thwart emerging
exploits like Log4Shell with malicious behavior protections for every host and
new detection rules for centralized alerting.



Elastic Blog


ELASTIC ENTERPRISE SEARCH 8.1: ENHANCED WEB CRAWLING AND SHAREPOINT ON-PREM...

In Elastic Enterprise Search 8.1, enhancements to the Elastic web crawler make
website content ingestion faster and more flexible than ever with partial crawls
and new debugging tools. Plus, a new addition to the Workplace Search prebuilt
connector...



Elastic Blog


ELASTIC OBSERVABILITY 8.1: VISIBILITY INTO AWS LAMBDA, CI/CD PIPELINES, AND MORE

With Elastic Observability 8.1, development teams can now get enhanced
visibility into AWS Lambda and CI/CD build pipelines, and leverage open
standards based instrumentation for unified data ingest and analysis across a
wide variety of data types.







WHAT ARE PORTS 9200 AND 9300 USED FOR?

Meta ElasticElastic Tips and Common Fixes
elasticsearch

You have selected 0 posts.

select all

cancel selecting


RECOMMENDED FOR YOU

 * Distributed Elastic Architectures
 * Elastic 7.16: Streamlined data integrations drive results that matter
 * Twilio
 * Accelerate app development and defend against novel attacks with Elastic 8.
 * Elastic 8.0: A new era of speed, scale, relevance, and simplicity


warkolmMark WalkomElastic Team Member
1
Jun 2020


[This is an extension on an older thread - Elasticsearch port 9200 or 9300?]

By default, Elasticsearch uses two ports to listen to external TCP traffic;

 * Port 9200 is used for all API calls over HTTP. This includes search and
   aggregations, monitoring and anything else that uses a HTTP request. All
   client libraries will use this port to talk to Elasticsearch
 * Port 9300 is a custom binary protocol used for communications between nodes
   in a cluster. For things like cluster updates, master elections, nodes
   joining/leaving, shard allocation

Historically, port 9300 was also used for connections from client libraries,
however this type of interaction is deprecated across our official clients, and
not supported elsewhere.

You can change the ports that Elasticsearch uses for this, via the http.port and
transport.port settings 762.

4

 * Elasticsearch port 9200 or 9300?94
 * Will es nodes connect with each other in 9200?3





Reply



SUGGESTED TOPICS

Topic Replies Views Activity Assign Email Connector to Multiple Rules
Elastic Security
1 64 23d Getting Unique Set of nested objects within aggregations
Elasticsearch
1 65 15d Is there another way to import template at boot?
Beats
filebeat heartbeat
4 128 10d Es 的攻击图数据怎么一次查询实现
中文提问与讨论
1 41 7d Windows Environment Variables not accessible when Logstash is run as a
service
Logstash
0 38 4d


WANT TO READ MORE? BROWSE OTHER TOPICS IN ELASTIC TIPS AND COMMON FIXES OR VIEW
LATEST TOPICS.

Share




© 2020. All Rights Reserved - Elasticsearch

 * Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and
   in other countries
 * Trademarks
 * Terms
 * Privacy
 * Brand
 * Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo
are trademarks of the Apache Software Foundation in the United States and/or
other countries.

 * 
 * 
 * 
 * 
 * 


Invalid date Invalid date




Press again to continue 0/1
Notice

We and selected third parties use cookies or similar technologies for technical
purposes and, with your consent, for other purposes as specified in the cookie
policy.

Learn more and customize
RejectAccept