Read from secondaries trade-offs in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does reading from secondaries in MongoDB mean?

It means querying data from secondary replica set members instead of the primary, which can reduce load on the primary and improve read scalability.

beginner

What is a main trade-off when reading from secondaries?

You might get stale data because secondaries replicate changes asynchronously and can lag behind the primary.

intermediate

How does reading from secondaries affect consistency?

It can reduce consistency guarantees because the data on secondaries may not reflect the most recent writes made to the primary.

intermediate

Why might an application choose to read from secondaries despite potential stale data?

To improve read throughput and reduce latency by distributing read load, especially for read-heavy workloads.

advanced

What is a common strategy to minimize stale reads when reading from secondaries?

Use read preferences like 'secondaryPreferred' with a maxStalenessSeconds setting to limit how stale the data can be.

What is a potential downside of reading from MongoDB secondaries?

A Data might be outdated due to replication lag

B Primary server load increases

C Writes become slower

D Secondaries cannot serve reads

Secondaries replicate asynchronously, so data can be slightly behind the primary.

Which read preference allows reading from secondaries but falls back to primary if no secondaries are available?

A primary

B secondary

C secondaryPreferred

D nearest

'secondaryPreferred' reads from secondaries if possible, otherwise from primary.

How can you limit how stale data can be when reading from secondaries?

A Disable journaling

B Use write concern majority

C Increase primary election timeout

D Set maxStalenessSeconds in read preference

maxStalenessSeconds restricts how old the data on secondaries can be for reads.

Why might an application prefer reading from the primary over secondaries?

A To increase read scalability

B To get the most up-to-date data

C To reduce primary load

D To avoid replication lag

Primary always has the latest data, so reading from it ensures strong consistency.

Which scenario benefits most from reading from secondaries?

A Read-heavy workloads with tolerance for slightly stale data

B Single server deployments

C Applications requiring strict consistency

D Write-heavy workloads

Reading from secondaries improves read throughput but may return slightly stale data.

Explain the trade-offs of reading from secondaries in MongoDB replica sets.

Think about what happens when data is copied asynchronously.

Describe strategies to reduce stale reads when using secondary reads in MongoDB.

Consider configuration options that control how fresh the data must be.