Alexander Preuß photo
Alexander Preuß

Table of Contents

Tutorial

How to unload a Pulsar topic

Introduction

In Apache Pulsar, unloading a topic is a helpful administrative action that forces the broker to release resources tied to a topic. This can be especially useful for rebalancing load, resolving temporary issues, or resetting state on the broker.

In this guide, we’ll walk through how to unload a topic directly from the web interface. No CLI required.

Navigating the Explorer

To get started, open the Explorer page. This is your main starting point for interacting with your Pulsar environment.

Once you are on the Explorer page, you'll see a list of tenants, the logical groups that help organize your messaging infrastructure. Each tenant contains one or more namespaces, which in turn contain the actual topics where your messages live.

Here’s a quick path through the structure:

  • Select a Tenant → reveals available Namespaces inside
  • Select a Namespace → shows all the Topics inside
  • Click on a Topic → opens the Topic Overview

This clear hierarchy ensures you always know exactly where you are in the system.

Unloading a Topic

Once you’ve selected a topic, you’ll land on its overview page. This page gives you general information about the topic, such as its configuration and metrics.

Look for the Manage button and click on it. In the context menu that opens, select Unload.

When you click Unload, here is what happens:

  • The broker closes connections to producers and consumers on this topic
  • (Cached) topic and subscription metadata is released
  • The topic becomes eligible to be reassigned to another broker

This actions is safe and quick - it does not delete any data and the topic will automatically be reassigned.

Wrapping Up

Unload a Pulsar topic is a powerful but simple operation when managing Pulsar clusters. With our Pulsar UI, you can get easy one-click access to all the go-to operations you need. Try it out next time you need to reset a stuck connection, reduce load on a broker or release some stale metadata!

Alexander Preuß photo
About the Author
Alexander Preuß is a seasoned expert in the data streaming field with extensive experience as a software engineer at both startups and large enterprises. Specializing in distributed systems, he has contributed to various open source projects, including Apache Flink, Apache Kafka, and Apache Pulsar, along with their ecosystems. Prior to founding Streamvisor, Alexander worked at Ververica (acquired by Alibaba) and StreamNative.

Let's stay in touch

Get notified of new developments or blogposts.
Checkmark icon
You've joined the mailing list!
Oops! Something went wrong while submitting the form.