apache / apache/pulsar

[Bug] Not able to set default backlog-quota retention policy , default retention policy and default TTL

Open
#22,226 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Version

pulsar helm chart version - 3.3.0
k8s version - v1.28.5+k3s1

### Minimal reproduce step

When installing pulsar using pulsar helm chart added these values to broker.configData
```
backlogQuotaDefaultRetentionPolicy: "consumer_backlog_eviction"
backlogQuotaDefaultLimitBytes: "322122547200"
backlogQuotaDefaultLimitSecond: "1209600"
defaultRetentionTimeInMinutes: "2880"
defaultRetentionSizeInMB: "-1"
ttlDurationDefaultInSeconds: "259200"
topicLevelPoliciesEnabled: "true"

```
exec in pulsar broker pod
do `bin/pulsar-admin namespaces get-backlog-quotas public/functions`

### What did you expect to see?

the output should be ->
`destination_storage BacklogQuotaImpl(limit=322122547200, limitSize=322122547200, limitTime=1209600, policy=consumer_backlog_eviction)`

### What did you see instead?

I get no output

same goes for retention policy and ttl -> i get null as output , but it should return the default ttl and default return policy values as output respectively

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start with the Pulsar Helm chart's broker.configData values and reproduce on Helm chart 3.3.0 with the listed Kubernetes version. Run pulsar-admin namespaces get-backlog-quotas public/functions and check the corresponding retention and TTL outputs; done means the configured default backlog quota, retention policy, and TTL are returned instead of empty or null results.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, java, kubernetes
Domain
backend, cli, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.