Skip to main content

You get the error "Operation not permitted on a capped collection". What might be the issue?

 The error:

"Operation not permitted on a capped collection"

comes from MongoDB, and it indicates that you're trying to perform an operation that is not allowed on a capped collection.

You get the error "Operation not permitted on a capped collection". What might be the issue?

πŸ” What Is a Capped Collection?

A capped collection in MongoDB is a special type of collection with:

  • Fixed size (in bytes or documents)

  • Automatic overwrites of the oldest documents when full

  • Insertion order preservation

  • High performance for insert + read workloads (e.g. logs, telemetry)

🚫 Operations Not Allowed on Capped Collections

The following operations will trigger this error:

❌ 1. Delete Specific Documents

db.logs.deleteOne({ level: "error" }) // ❌ Not allowed

❌ 2. Update with Document Size Increase

You can't update a document in a capped collection if the updated version is larger than the original.

❌ 3. Remove Documents with remove() or deleteMany()

Only automatic removal by the capped size is allowed.

❌ 4. FindAndModify that Deletes or Replaces

Can't use findAndModify to delete or replace documents in a capped collection.

✅ How to Fix or Work Around It

πŸ›  1. Avoid Deletes and Size-Increasing Updates

  • Only use in-place updates that don't change document size.

  • Use capped collections only for append-only use cases (like logs).


// This is allowed db.logs.updateOne({ _id: ... }, { $set: { level: "warn" } })

πŸ›  2. Check if the Collection Is Capped

To confirm:

db.collection.stats().then(stats => console.log(stats.capped))

πŸ›  3. Convert to a Normal Collection (If Needed)

If you need deletes or flexible updates:

  1. Create a new normal collection:

    db.createCollection("new_logs")
  2. Copy data:

    db.new_logs.insertMany(db.logs.find().toArray())
  3. Drop the old capped collection:

    db.logs.drop()
  4. Rename:

    db.new_logs.renameCollection("logs")

πŸ’‘ When Should You Use a Capped Collection?

Only when:

  • You have append-only data

  • Document size is predictable

  • You need fast inserts and fixed-size storage

e.g., log streams, sensor data, circular buffers

Popular posts from this blog

How does BGP prevent routing loops? Explain AS_PATH and loop prevention mechanisms.

 In Border Gateway Protocol (BGP), preventing routing loops is critical — especially because BGP is the inter-domain routing protocol used to connect Autonomous Systems (ASes) on the internet. πŸ”„ How BGP Prevents Routing Loops The main mechanism BGP uses is the AS_PATH attribute . πŸ” What is AS_PATH? AS_PATH is a BGP path attribute that lists the sequence of Autonomous Systems (AS numbers) a route has traversed. Each time a route is advertised across an AS boundary, the local AS number is prepended to the AS_PATH. Example: If AS 65001 → AS 65002 → AS 65003 is the route a prefix has taken, the AS_PATH will look like: makefile AS_PATH: 65003 65002 65001 It’s prepended in reverse order — so the last AS is first . 🚫 Loop Prevention Using AS_PATH ✅ Core Mechanism: BGP routers reject any route advertisement that contains their own AS number in the AS_PATH. πŸ” Why It Works: If a route makes its way back to an AS that’s already in the AS_PATH , that AS kno...

Explain the Angular compilation process: View Engine vs. Ivy.

 The Angular compilation process transforms your Angular templates and components into efficient JavaScript code that the browser can execute. Over time, Angular has evolved from the View Engine compiler to a newer, more efficient system called Ivy . Here's a breakdown of the differences between View Engine and Ivy , and how each affects the compilation process: πŸ”§ 1. What Is Angular Compilation? Angular templates ( HTML inside components) are not regular HTML—they include Angular-specific syntax like *ngIf , {{ }} interpolation, and custom directives. The compiler translates these templates into JavaScript instructions that render and update the DOM. Angular uses Ahead-of-Time (AOT) or Just-in-Time (JIT) compilation modes: JIT : Compiles in the browser at runtime (used in development). AOT : Compiles at build time into efficient JS (used in production). 🧱 2. View Engine (Legacy Compiler) ➤ Used in Angular versions < 9 πŸ” How It Works: Compiles templat...

What is Zone.js, and why does Angular rely on it?

Zone.js is a library that Angular relies on to manage asynchronous operations and automatically trigger change detection when necessary. Think of it as a wrapper around JavaScript’s async APIs (like setTimeout , Promise , addEventListener , etc.) that helps Angular know when your app's state might have changed. πŸ” What is Zone.js? Zone.js creates an execution context called a "Zone" that persists across async tasks. It tracks when tasks are scheduled and completed—something JavaScript doesn't do natively. Without Zone.js, Angular wouldn’t automatically know when user interactions or async events (like an HTTP response) occur. You’d have to manually tell Angular to update the UI. ⚙️ Why Angular Uses Zone.js ✅ 1. Automatic Change Detection Zone.js lets Angular detect when an async task finishes and automatically run change detection to update the UI accordingly. Example: ts setTimeout ( () => { this . value = 'Updated!' ; // Angular know...