Exception in clusters with embedded and standalone nodes #40
Labels
Comments
|
The elasticsearch script currently set the preferIPv4Stack to true because of problems I had with using the default in Java (which defaults to the machine). This menas that you need to either change the flag on the script, or set the flag on the embedded client side. I need to revisit this decision to set the ipv4 flag to true and use the JVM default, but it needs to work well out of the box, without needing to set it explicitly. See this thread for why I default to ipv4: http://old.nabble.com/Suspect-warning-in-jgroups-2.8.0-CR6-to26560364.html#a26560364 |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
s1monw
pushed a commit
that referenced
this issue
Jun 5, 2015
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
May 24, 2018
Each `Publication` implements a small state machine. Today the transitions of this state machine are spread throughout the `Publication` class, which makes it hard to analyse and easy to break as things evolve. This commit extracts this state machine into a class of its own so that it is easier to see the effects of any future changes.
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we add a new challenge `index-and-query-logs-fixed-daily-volume` which bulk-indexes documents and issues queries concurrently. Bulk-indexing throughput is throttled at different utilization levels that are controlled by a new scheduler implementation that runs at peak throughput during warmup and throttles it during measurement according to the targeted utilization. Relates elastic#40
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run a cluster made up of embedded and standalone nodes, former ones seems not to be able to connect to latter ones, and I get the following log messages on embedded nodes:
OOB-1,elasticsearch,caffeine.local-16363 -
jgroups.pbcast.NAKACK - caffeine.local-16363: dropped message from
caffeine.local-17690 (not in xmit_table), keys are
[caffeine.local-16363], view=[caffeine.local-16363|0]
[caffeine.local-16363]
The problem seems to be related to JGroups which, on IPv6-enabled machines, prefers IPv6 addresses over IPv4 ones, but embedded instances aren't able to guess a proper IPv6 address.
That can be fixed by:
Specifying java.net.preferIPv4Stack=true on the embedded node, forcing the use of IPv4.
or
Specifying java.net.preferIPv4Stack=false and java.net.preferIPv6Stack=false on the standalone node, apparently forcing JGroups to take the proper default.
The text was updated successfully, but these errors were encountered: