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
Possible configuration problem in the pubsub rabbitmq component #2764
Comments
@arturotrenard I am not sure I understand the issue. Could you help us understand please? |
Yes, of course, let's say that the user indicates that the queue should not be durable. In the code it is already stated that it is. |
Thanks, we'll get this fixed |
Then I will write to you on discord about the performance issue. Because I have implemented a connection pool management for rabbitMQ and in my local tests without putting much iron and pointing to a standard RabbitMQ and the results exceed 20k/s, something that I did not achieve with the component and that is why I comment for the group. I have not |
/assign |
Once Dapr 1.11 is out please try to reproduce this problem @arturotrenard. Hopefully the PR from @SpikeWong actually addressed the issue. |
@arturotrenard can you try out Dapr 1.11 RC5? https://github.com/dapr/dapr/releases/tag/v1.11.0-rc.5 to see if you can reproduce this? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
|
Expected Behavior
Hello guys I think there is a problem here if you want to change the configuration
Actual Behavior
Steps to Reproduce the Problem
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: