[BUG]

Open
#816 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with AmqpTopicManager and QueueContainer, then trace the logged BrokerService ServiceUnitNotReadyException for the persistent topic. Reproduce with Pulsar 2.9.2 and AOP 2.9.1 if possible, and use the repeated lookup and queue-topic errors as the baseline for verifying that the failure no longer persists.

Written by the indexing model from the issue text.

Description

type/bug

Describe the bug
Failed to getTopic persistent

To Reproduce
pulsar version 2.9.2
aop version 2.9.1
After a period of normal operation, this problem occurred

INFO  io.streamnative.pulsar.handlers.amqp.AmqpTopicManager - Find getBrokerServiceUrl Optional[LookupResult [type=BrokerUrl, lookupData=LookupData{brokerUrl=pulsar://172.22.1.17:36650, brokerUrlTls=null, httpUrl=http://172.22.1.17:38080, httpUrlTls=null}]], return Topic: persistent://public/nova/__amqp_queue__scheduler
2023-02-13T09:07:19,825+0800 [pulsar-io-4-85] WARN  org.apache.pulsar.broker.service.BrokerService - Namespace bundle for topic (persistent://public/nova/__amqp_queue__scheduler) not served by this instance. Please redo the lookup. Request is denied: namespace=public/nova
2023-02-13T09:07:19,825+0800 [pulsar-io-4-85] ERROR io.streamnative.pulsar.handlers.amqp.AmqpTopicManager - Failed to getTopic persistent://public/nova/__amqp_queue__scheduler. exception: org.apache.pulsar.broker.service.BrokerServiceException$ServiceUnitNotReadyException: Namespace bundle for topic (persistent://public/nova/__amqp_queue__scheduler) not served by this instance. Please redo the lookup. Request is denied: namespace=public/nova
2023-02-13T09:07:19,825+0800 [pulsar-io-4-85] WARN  io.streamnative.pulsar.handlers.amqp.QueueContainer - [public/nova][scheduler] Queue topic did not exist.
2023-02-13T09:07:19,826+0800 [pulsar-io-4-85] INFO  io.streamnative.pulsar.handlers.amqp.AmqpTopicManager - Find getBrokerServiceUrl Optional[LookupResult [type=BrokerUrl, lookupData=LookupData{brokerUrl=pulsar://172.22.1.17:36650, brokerUrlTls=null, httpUrl=http://172.22.1.17:38080, httpUrlTls=null}]], return Topic: persistent://public/nova/__amqp_queue__scheduler
2023-02-13T09:07:19,826+0800 [pulsar-io-4-85] WARN  org.apache.pulsar.broker.service.BrokerService - Namespace bundle for topic (persistent://public/nova/__amqp_queue__scheduler) not served by this instance. Please redo the lookup. Request is denied: namespace=public/nova
2023-02-13T09:07:19,826+0800 [pulsar-io-4-85] ERROR io.streamnative.pulsar.handlers.amqp.AmqpTopicManager - Failed to getTopic persistent://public/nova/__amqp_queue__scheduler. exception: org.apache.pulsar.broker.service.BrokerServiceException$ServiceUnitNotReadyException: Namespace bundle for topic (persistent://public/nova/__amqp_queue__scheduler) not served by this instance. Please redo the lookup. Request is denied: namespace=public/nova
2023-02-13T09:07:19,826+0800 [pulsar-io-4-85] WARN  io.streamnative.pulsar.handlers.amqp.QueueContainer - [public/nova][scheduler] Queue topic did not exist.

Screenshots
image

Additional context
Can you take a look at it for me

Dominant language
Java
Stars
123
Forks
41
Avg merge
4h 43m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamnative/aop

All issues in streamnative/aop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.