Deleting and closing indexes in Elasticsearch - Time & Space Complexity

Time Complexity: Deleting and closing indexes

O(n)

Understanding Time Complexity

When deleting or closing indexes in Elasticsearch, it's important to understand how the time taken grows as the number of indexes increases.

We want to know how the cost changes when more indexes are involved.

Scenario Under Consideration

Analyze the time complexity of the following Elasticsearch commands.

DELETE /my_index

POST /my_index/_close

POST /_all/_close

DELETE /index_1,index_2,index_3
    

This code deletes or closes one or multiple indexes by name or all indexes at once.

Identify Repeating Operations

Look for repeated work done when handling multiple indexes.

• Primary operation: Elasticsearch processes each index separately to delete or close it.
• How many times: Once per index requested in the command.

How Execution Grows With Input

As the number of indexes to delete or close grows, the work grows roughly the same way.

Input Size (n)	Approx. Operations
10	About 10 index operations
100	About 100 index operations
1000	About 1000 index operations

Pattern observation: The time grows linearly as you add more indexes to delete or close.

Final Time Complexity

Time Complexity: O(n)

This means the time to delete or close indexes grows directly in proportion to how many indexes you handle.

Common Mistake

[X] Wrong: "Deleting or closing multiple indexes happens instantly regardless of how many there are."

[OK] Correct: Each index requires its own processing, so more indexes mean more time needed.

Interview Connect

Understanding how operations scale with input size helps you explain system behavior clearly and shows you can think about performance in real situations.

Self-Check

"What if we delete indexes in parallel instead of one by one? How would the time complexity change?"