Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn MongoDB 4.x

You're reading from   Learn MongoDB 4.x A guide to understanding MongoDB development and administration for NoSQL developers

Arrow left icon
Product type Paperback
Published in Sep 2020
Publisher Packt
ISBN-13 9781789619386
Length 610 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Doug Bierer Doug Bierer
Author Profile Icon Doug Bierer
Doug Bierer
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Preface 1. Section 1: Essentials
2. Introducing MongoDB 4.x FREE CHAPTER 3. Setting Up MongoDB 4.x 4. Essential MongoDB Administration Techniques 5. Section 2: Building a Database-Driven Web Application
6. Fundamentals of Database Design 7. Mission-Critical MongoDB Database Tasks 8. Using AJAX and REST to Build a Database-Driven Website 9. Section 3: Digging Deeper
10. Advanced MongoDB Database Design 11. Using Documents with Embedded Lists and Objects 12. Handling Complex Queries in MongoDB 13. Section 4: Replication, Sharding, and Security in a Financial Environment
14. Working with Complex Documents Across Collections 15. Administering MongoDB Security 16. Developing in a Secured Environment 17. Deploying a Replica Set 18. Replica Set Runtime Management and Development 19. Deploying a Sharded Cluster 20. Sharded Cluster Management and Development 21. Other Books You May Enjoy

What happens if a server goes down?

If a replica set member fails to respond to the regularly scheduled heartbeat within a predefined interval, the other members of the replica set assume it has failed and hold an election (https://docs.mongodb.com/manual/core/replica-set-elections/#replica-set-elections). A new primary is elected, which immediately starts accepting read and write requests and replicating its database. The following diagram illustrates the situation before and after an election:

Each member server has one vote. On the left side of the preceding diagram, the primary has gone offline. The remaining secondaries in the replica set hold an election. After the election, as shown on the right side of the diagram, the topmost secondary is elected as the new primary.

In order to avoid a voting deadlock (for example, where an even number of remaining servers are split over who becomes the new primary), it is possible to establish arbiters. An arbiter is a server that is part of...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime