apache / apache/pulsar

delete namespace will fail if cache not updated immediately

Open
#15,618 1 comment 0 reactions 0 assignees View on GitHub
Stale type/bug
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. create namespace which routed to broker 1
2. delete namesapce which routed to broker 2

broker2 find no ns in cache,will return fail

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]

**Additional context**
Add any other context about the problem here.
same issue : https://github.com/apache/pulsar/issues/15555

Contributor guide

Open the contributing guide

Research direction

Start with the reproduction steps: create a namespace routed to broker 1, then delete it through broker 2, and compare the behavior with issue 15555. Investigate how namespace cache state is used during deletion; done means deletion succeeds even when the receiving broker's cache has not updated immediately.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.