apache / apache/pulsar

When the bookie storage is about to reach the threshold and then returns to the normal level, the producer cannot write topic normally

Open
#11,271 1 comment 0 reactions 0 assignees View on GitHub
lifecycle/stale type/bug
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 22h
Merged PRs (30d)
142

Description

**Describe the bug**
Pulsar v2.6.2

When the bookie storage is about to reach the threshold and then returns to the normal level, the producer cannot write topic normally.

1、Producer log:
![image](https://user-images.githubusercontent.com/54351417/125018546-eae57a80-e0a7-11eb-9f9e-1eafaf6cd19b.png)
2、Bookies storage:
![image](https://user-images.githubusercontent.com/54351417/125018606-051f5880-e0a8-11eb-8849-2374590e3652.png)
3、Clear backlog, Bookies storage returns to the normal level:
![image](https://user-images.githubusercontent.com/54351417/125018612-08b2df80-e0a8-11eb-9513-302e96d9206e.png)
4、Restart Producer logs:
![image](https://user-images.githubusercontent.com/54351417/125018686-2ed87f80-e0a8-11eb-9b6a-3304c3da9f32.png)
5、Code:
![image](https://user-images.githubusercontent.com/54351417/125018743-4b74b780-e0a8-11eb-9abe-cb64e3fdad2c.png)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported sequence on Pulsar v2.6.2: let bookie storage approach its threshold, clear the backlog so storage returns to normal, and check whether the producer can write again without restarting. Review the producer logs, bookie storage observations, and attached code screenshot to identify the affected storage-threshold path. Done means producers resume normal topic writes after storage recovers.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.