Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

ElasticSearch cluster status yellow

Solved1.20K views12th August 2022elastic cluster Elasticsearch
0
Philip Argent [DevOps Enabler]579 1st August 2022 0 Comments

We've had an ES cluster installed locally on our dev DMA pair, checking the cluster health status it's coming back yellow, looking at the indexes all the ones created by DataMiner are being created with 3 primary shards and 2 replicas in a 2 node cluster.

Why are we getting 3 shards for each index, surely we only need 1?

Why are the replicas set to 2 instead of 1?

As far as I'm aware these nodes were installed using the "Install Indexing Engine..." under Search & Indexing in the System Centre.

Thomas Deweer [SLC] Answered question 1st August 2022

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
Thomas Deweer [SLC]286 Posted 1st August 2022 3 Comments

Hello,

I would not think about the amount of primary shards we configure. This is purely related to scaling and 3 is the default and should be fine.
We configure it to 2 as default (replication). This was just a choice made by us but it's a 'magic' number. You could change this. However, cluster health yellow is normal in this case. It's not bad, yellow is just fine. If you add more nodes, it will obviously turn green but there's no side effects apart from fewer replication.

I would like to point out that 2 nodes is worst case scenario for an Elastic cluster. A detailed explenation of the why, you can find here: Configuring the master nodes | DataMiner Docs.

Srikanth Mandava [SLC] [DevOps Advocate] Posted new comment 2nd August 2022
Philip Argent commented 1st August 2022

Thanks Thomas,
I’d done some more reading on primary and replication, which makes sense on the split of each index for scaling and load balance.
This is just our dev system so will only ever have a 2 node cluster. It would be nice to change the default replication to 1 to get it to go green, if you could point me in the right direction for changing this setting.

Srikanth Mandava [SLC] [DevOps Advocate] commented 2nd August 2022

Keeping it as two node cluster will result in the ES stability and will require some maintenance, data loss and re-configuration when it results in the split brain situations.

Following is the command you can run to update the ES configuration for number of replicas. .

curl -XPUT ‘localhost:9200/_settings’ -d ‘
{
“index” : {
“number_of_replicas” : 1
}
}
‘

Philip Argent commented 12th August 2022

FYI as NATS doesn’t play ball nicely with 2 node clusters, a single hot redundant pair doesn’t really work anymore if the node with the lower IP goes offline, as it causes the other node to crash, so we’d only have a 50% chance of a cluster that was still running anyway.
We’ve got the number of nodes for an active cluster set to 2 to prevent the split brain issue.

You are viewing 1 out of 1 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin