Index usage verification in MongoDB - Step-by-Step Execution

Concept Flow - Index usage verification

Run Query

↓

MongoDB Query Planner

↓

Check Available Indexes

↓

Choose Index or Collection Scan

↓

Execute Query Using Chosen Plan

↓

Explain Output Shows Index Usage

This flow shows how MongoDB decides to use an index or not when running a query and how to verify it using explain.

Execution Sample

MongoDB

db.users.find({age: 30}).explain('executionStats')

This command runs a query to find users aged 30 and shows detailed stats including index usage.

Execution Table

Step	Action	Query Planner Decision	Index Used	Output Detail
1	Run query db.users.find({age: 30})	Analyzing query	N/A	Preparing to plan
2	Check indexes on 'age'	Indexes found: age_1	age_1	Index available for 'age' field
3	Choose plan	Index scan chosen over collection scan	age_1	Using index to filter documents
4	Execute query	Index scan performed	age_1	Documents matching age=30 retrieved
5	Return explain output	Shows execution stats	age_1	Index used: true, keys examined, docs returned
6	End	Query complete	age_1	Index usage verified in explain output

💡 Query execution finished with index usage confirmed by explain output

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Index Used	None	age_1 found	age_1 chosen	age_1 used	age_1 confirmed
Query Plan	None	Indexes checked	Index scan plan	Executing index scan	Plan executed

Key Moments - 2 Insights

Why does the explain output show 'COLLSCAN' instead of an index name?

If the explain output shows 'COLLSCAN', it means MongoDB did not use any index and scanned the whole collection. This can happen if no suitable index exists or the query does not match any index. See execution_table row 3 where index choice is made.

How can I tell from explain output that an index was actually used?

Look for 'indexName' field and 'stage' showing 'IXSCAN' in the explain output. In execution_table row 5, the output detail confirms index usage with keys examined and index name.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does MongoDB decide which index to use?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Check the 'Query Planner Decision' column in execution_table row 3.

According to variable_tracker, what is the value of 'Index Used' after Step 4?

A age_1 found

B age_1 used

C None

D age_1 confirmed

💡 Hint

Look at the 'Index Used' row and the 'After Step 4' column in variable_tracker.

If no index exists on the queried field, what would the execution_table show at Step 3?

A Index scan chosen over collection scan

B Query aborted

C Collection scan chosen due to no index

D Index created automatically

💡 Hint

Refer to key_moments explanation about 'COLLSCAN' and execution_table Step 3.

Concept Snapshot

MongoDB uses indexes to speed up queries.
Use db.collection.find(query).explain('executionStats') to see if an index is used.
Explain output shows query plan and index usage.
If no index matches, MongoDB does a collection scan.
Check 'stage' and 'indexName' in explain to verify index usage.

Full Transcript

This visual execution shows how MongoDB verifies index usage when running a query. First, the query runs and the query planner checks available indexes. If an index matches the query, MongoDB chooses an index scan plan instead of scanning the whole collection. The query executes using the chosen index. The explain output then shows detailed execution stats including whether an index was used. Variables like 'Index Used' track the index state through each step. Key moments clarify why sometimes MongoDB does not use an index and how to read the explain output to confirm index usage. The quiz tests understanding of when and how MongoDB picks and uses indexes during query execution.