Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Update Elasticsearch configuration to help improve full cluster restart (74709)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 9601Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

After a full cluster shutdown (ie, all nodes have been shutdown), elasticsearch can sometimes fail to form a cluster when the nodes are restarted. The cluster health will be red with lots of unassigned shards and the elasticsearch logs will have errors connecting to or finding the primary node.

Elasticsearch is showing a red state after a full cluster stop and start.

Cause

This issue is caused when plugin for elasticsearch that asks IDM for the list of nodes that are expected to be in the cluster. It uses that list to determine how many nodes it should be able to see before a primary can be elected and the cluster formed. When all the nodes have been shutdown (i.e. there is not an existing primary running), when the first node is restarted, elasticsearch will start faster than IDM, preventing it from getting the list of nodes to expect. The default configuration results in elasticsearch assuming it does not need more nodes to be primary, but then discovers it has data shards missing (because they exist on the other nodes that are still down). This results in it being in a bad state, preventing the cluster to form properly.

Resolution

To resolve this issue:

change the configuration so that on restart all the nodes know to expect more than one node in the cluster. This will make the first node wait for a second node to comes up before starting to form a cluster.  It also gives more time for the full cluster to restart.

On each node, edit /opt/vmware/elasticsearch/config/elasticsearch.yml file to add these lines, using the formulas in <> for setting the values based on the number of nodes in your cluster (N):

Note: if your environment has “N” number of nodes, use the following formula:

discovery.zen.minimum_master_nodes: <N+1/2>
gateway.recover_after_nodes: <N+1/2>
gateway.expected_nodes: <N>
gateway.recover_after_time: 10m

Example: For a 3-node service cluster:

discovery.zen.minimum_master_nodes: 2
gateway.recover_after_nodes: 2
gateway.expected_nodes: 3
gateway.recover_after_time: 10m

Note: This configuration is only needed on a restart, so you do not need to restart elasticsearch after adding the configuration.
Note: Make sure you do not have any leading spaces, duplicate entries or incorrect syntax as these will prevent elasticsearch from parsing the config file and starting at all.

Workaround

This issue can be temporarily be fixed by restarting elasticsearch on just that first node (once the other two nodes are up) with the following command:

service elasticsearch restart

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
How to get Postgres version information in vRealize Operations Manager (74793)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE Access

VMware Site Recovery Manager

VMware Identity Manager

Related Versions:

VMware Identity Manager 3.0

VMware Identity Manager 2.x

Take Our Survey

Support Assistant