Search is not working properly on cluster 2 node setup

Hi Elastic team,

I am using Elasticsearch service on 2 node setup. Both the nodes have default configuration (elasticsearch.yml).

Case : Suppose there are 50 entries in a list to search from. A new entry ("newentry51") is added in the list making the total count of entries = 51. After restarting both the nodes, if I try to search "newentry51", then "newentry51" will come in results only on every alternate occasion i.e. (1st time search - getting "newentry51" in results, 2nd time search - not getting, 3rd time search - getting, and so on...).

Please suggest if there is any configuration to automatically refresh search index after rebooting the nodes or if there is any approach to solve this problem.

------------------------elasticsearch.yml------------------------------ log-collector /var/cache/secmgt-elastic-data/log-collector
path.logs: /var/log/elasticsearch
node.master: true true
#bootstrap.memory_lock: true # this one added new
discovery.zen.hosts_provider: file [“”, "”]
# set the master node IP if the master is remote

# Configuration to check out of memory error
indices.fielddata.cache.size:  40%
indices.breaker.fielddata.limit: 60%
indices.breaker.request.limit: 40% 70%
# Configuration to enable performance Writes
#index.translog.flush_threshold_size: 1gb //need to set
#index.refresh_interval: 10s //need to set
# set the following only on SSD, default is good for spin disk 100mb
bootstrap.system_call_filter: false x.x.x.x
network.publish_host: _eth0_

Setup Details : cluster 2-node setup

*This problem is happening after VM reboot


Welcome to our community! :smiley:

Please share an example that we can use to replicate this, eg documents and mappings, your search request etc.

Please check the description, I have shared configurations and some extra details in the end. Also there is an example in the description given to follow.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.