Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

standalone模式下,开启事务时,pulsar2.8.0不能正常使用。急急急! #11481

Closed
qiansheng2 opened this issue Jul 28, 2021 · 4 comments
Labels
lifecycle/stale type/bug The PR fixed a bug or issue reported a bug

Comments

@qiansheng2
Copy link

qiansheng2 commented Jul 28, 2021

Describe the bug
standalone模式下,开启事务时,pulsar2.8.0不能正常使用

To Reproduce
Steps to reproduce the behavior:

  1. Download 2.8.0 and unzip it
  2. Modify the conf to enable the transaction
  3. Start by:pulsar standalone
  4. Got the exceptiion when program running

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

Screenshots
image
image

image

Desktop (please complete the following information):

  • OS: Ubuntu 20.04

Additional context
据说是个bug,希望能在2.8.1发布时修改,谢谢

@qiansheng2 qiansheng2 added the type/bug The PR fixed a bug or issue reported a bug label Jul 28, 2021
@qiansheng2 qiansheng2 changed the title standalone模式下,开启事务时,pulsar2.8.0不能正常启动。急急急! standalone模式下,开启事务时,pulsar2.8.0不能正常使用。急急急! Jul 28, 2021
@codelipenghui
Copy link
Contributor

@liangyepianzhou I think you already start investigate this issue right?

@liangyepianzhou
Copy link
Contributor

@codelipenghui
Yes, the problem is clear.
I'm trying to solve and write tests for it.

codelipenghui pushed a commit that referenced this issue Aug 10, 2021
## Modivation
Fix the Issue of #11481
In standalone mode, pulsar 2.8.0 cannot be used normally when the transaction is started

## CauseBy
```getTopic```was executed  twice when FunctionWorkService .
```getTopicIfExists```make ```createIfMissing = false``` When the execution ends.
```PersistentSubscription```  will create a ledger for the subscription  when transaction was turned on. 
```new MetadataNotFoundException("Managed ledger not found")```was thrown when calling ```MetaStoreImpl::getManagedLedgerInfo``` 
## implement   
Create a separate ManagerLedgerConfig for PendingAck
## verify 
Add testSubscriptionRecreateTopic in TransactionTest
hangc0276 pushed a commit that referenced this issue Aug 12, 2021
## Modivation
Fix the Issue of #11481
In standalone mode, pulsar 2.8.0 cannot be used normally when the transaction is started

## CauseBy
```getTopic```was executed  twice when FunctionWorkService .
```getTopicIfExists```make ```createIfMissing = false``` When the execution ends.
```PersistentSubscription```  will create a ledger for the subscription  when transaction was turned on.
```new MetadataNotFoundException("Managed ledger not found")```was thrown when calling ```MetaStoreImpl::getManagedLedgerInfo```
## implement
Create a separate ManagerLedgerConfig for PendingAck
## verify
Add testSubscriptionRecreateTopic in TransactionTest

(cherry picked from commit daf457d)
@codelipenghui
Copy link
Contributor

The issue had no activity for 30 days, mark with Stale label.

bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this issue Mar 18, 2022
## Modivation
Fix the Issue of apache#11481
In standalone mode, pulsar 2.8.0 cannot be used normally when the transaction is started

## CauseBy
```getTopic```was executed  twice when FunctionWorkService .
```getTopicIfExists```make ```createIfMissing = false``` When the execution ends.
```PersistentSubscription```  will create a ledger for the subscription  when transaction was turned on. 
```new MetadataNotFoundException("Managed ledger not found")```was thrown when calling ```MetaStoreImpl::getManagedLedgerInfo``` 
## implement   
Create a separate ManagerLedgerConfig for PendingAck
## verify 
Add testSubscriptionRecreateTopic in TransactionTest
@tisonkun
Copy link
Member

Closed by #11494.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants