Skip to content

Commit 9b8f3ae

Browse files
kallimachoskay-kim
authored andcommitted
DOCS-4578 Clarify global locks for index replication
1 parent 895a528 commit 9b8f3ae

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

source/core/index-creation.txt

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -124,13 +124,14 @@ Building Indexes on Secondaries
124124
background. Previously all index builds on secondaries were in the
125125
foreground.
126126

127-
A foreground index build on a :term:`primary` replicates as a foreground index
128-
build on :term:`replica set` :term:`secondaries <secondary>`. The replication
129-
worker acquires a global DB lock that queues reads and writes to all databases
130-
on the indexing server.
131-
132-
A background index build on a primary replicates as a background index build on
133-
secondaries. Secondary reads are not affected.
127+
A foreground index build on a :term:`primary` requires a global DB lock. It
128+
replicates as a foreground index build on :term:`replica set`
129+
:term:`secondaries <secondary>`, and the replication worker takes a global DB
130+
lock that queues reads and writes to all databases on the indexing server.
131+
132+
A background index build on a primary replicates as background index builds on
133+
secondaries. The replication worker does not take a global DB lock, and
134+
secondary reads are not affected.
134135

135136
In both cases, index operations on replica set secondaries begin after the
136137
primary finishes building the index.

0 commit comments

Comments
 (0)