Feature to use TransportClient instead of NodeClient #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update for elasticsearch 0.18.7
…to the hadoop cache misses
Fixes Wonderdog Pig 0.10 compatability issues and issues 5, 6, 7 and PIG-2792
Main advantage of this is to avoid "too many open files" error on hadoop workers.
… addresses handling for transport client.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With a large cluster, using NodeClient it is possible to encounter 'too many open files' errors due to the full-mesh connections between each elasticsearch node (including hadoop workers).
To counter that, I added the possibility to use TransportClient and define the desire entry-point nodes, thus limiting the number of connections each hadoop workers has. Using this type of client introduce 'double-hop' request for indexing. So far, I didn't saw much decrease in performance, but there is certainly one, which is counterbalanced by the ability to use all the nodes on the cluster.
Feel free to accept the pull request, but I am using it in production for 1-2 weeks without any issues.