Comments (1)
Hi @nobozo
- A new reader, such as yours truly, will wonder why Node 1 sent the request to Node 2, given that there's a shard replica containing the requested document on Node 1. Why the extra step?
A client may be sending all requests to a single node, which would mean that only that node would do any work. Instead, all requests are round-robin'ed around all shard copies.
There should be a 3rd step shown here showing where Node 2 returns the document. I think it's returned to Node 1, but I'm not 100% sure. Figure 9, on the previous page, shows the equivalent step.
Actually the previous diagram doesn't include the step that you mention. It has a 3rd step, but it relates to a different part of the process. That said, I've added a third step to make it more explicit.
I'm curious about the reason why the node returning the results is the node receiving the request rather than the node that performed the query/update. Is this because there's already a network connection between the client and the receiving node (e.g. Node 1 in Figure 10) so that the response doesn't involve opening a new connection between the node the performed the query/update (Node 2 in Figure 10) and the client? I could see how a firewall might block this.
Exactly. You can't push responses to HTTP clients, only return them where the connection is opened. You could potentially redirect the client to the right node but, as you say, firewalls could interfere with that process.
from elasticsearch-definitive-guide.
Related Issues (20)
- Cluster Health - Drilling Deeper: Finding Problematic Indices - clarifications
- I can't visit the test data page HOT 1
- Mention a link to `FlakeID scheme` explanation.
- tribe
- Possible grammar mistake
- Date Math Typo
- prefix not result
- GET cannot use body HOT 1
- String is no longer a type
- Aggregations do not work because of disabled fielddata
- Sense/Kibana installation and links
- missing value in example query
- text exact match example outdated
- Outdated doc about the parent/child relationship (mapping, indexing, query syntax)
- A mapping example from the doc, gives `mapper_parsing_exception` error HOT 5
- Mismatch between query and explanation
- Enhancement Request: Amend Circuit Breakers Discussion To Include A Discussion of Maximum Cluster Operating Limits HOT 2
- [DOCS] Replace `/master/` and `/current/` references to Elasticsearch Reference Guide
- [Question] What version of Elasticsearch is the guide currently targeting? HOT 1
- can't start the doc
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elasticsearch-definitive-guide.