New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate network settings, common tcp settings, and generalized port settings #174
Labels
Comments
Consolidate network settings, common tcp settings, and generalized port settings, closed by 723e47a. |
The docs should also be simplified and remove the netty sub module from it. |
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
This has been fixed in Tika 1.8. See https://issues.apache.org/jira/browse/TIKA-1548 We can now remove that call in `AttachmentMapper` class. Closes elastic#174. (cherry picked from commit eacb040)
costin
pushed a commit
that referenced
this issue
Dec 6, 2022
🤖 Generated PR to keep ESQL development branch up to date
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we enable GC logs for all race configurations which have the G1 garbage collector explicitly enabled. Relates elastic#168
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
add description of our retry policy for events
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create common tcp settings for
network.tcp.no_delay
,network.tcp.keep_alive
,network.tcp.reuse_address
,network.tcp.send_buffer_size
, andnetwork.tcp.receive_buffer_size
. Specific settings still exists (the netty ones per module of transport/http/memcached).Also, create a more simplified setting for ports. Transport port can be set using
transport.tcp.port
(on top of the currenttransport.netty.port
), HTTP port can be set usinghttp.port
(on top ofhttp.netty.port
), and memcached port can be set usingmemcached.port
(on top ofmemcached.netty.port
).The text was updated successfully, but these errors were encountered: