Replies: 6 comments 2 replies
-
|
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
|
We cannot suggest anything with this much information. Consider sharing an executable way to reproduce and node logs. The sharing plugin hasn't changed at all in 3.9, here is the entire diff: diff --git a/deps/rabbitmq_sharding/src/rabbit_sharding_shard.erl b/deps/rabbitmq_sharding/src/rabbit_sharding_shard.erl
index 20a0df66fb..16a4d1ccd7 100644
--- a/deps/rabbitmq_sharding/src/rabbit_sharding_shard.erl
+++ b/deps/rabbitmq_sharding/src/rabbit_sharding_shard.erl
@@ -90,8 +90,8 @@ declare_queue(XName, Durable, N, Node) ->
ok
catch
_Error:Reason ->
- _ = rabbit_log:error("sharding failed to declare queue for exchange ~p"
- " - soft error:~n~p~n",
+ rabbit_log:error("sharding failed to declare queue for exchange ~p"
+ " - soft error:~n~p",
[exchange_bin(XName), Reason]),
error
end.
@@ -119,7 +119,7 @@ binding_action(F, XName, RoutingKey, N, Node, ErrMsg) ->
?SHARDING_USER) of
ok -> ok;
{error, Reason} ->
- _ = rabbit_log:error(ErrMsg, [QBin, exchange_bin(XName), Reason]),
+ rabbit_log:error(ErrMsg, [QBin, exchange_bin(XName), Reason]),
error
end.Try it for yourself: git diff v3.8.x..v3.9.x -- deps/rabbitmq_sharding/src |
Beta Was this translation helpful? Give feedback.
-
|
Can someone support with it? |
Beta Was this translation helpful? Give feedback.
-
|
We've also been seeing this problem. Error logOur 3.8.29 cluster is completely fine, and has been through multiple point release upgrades. |
Beta Was this translation helpful? Give feedback.
-
|
i also have this problem, 3.8.x is fine, but 3.9.x and 3.10.x is fail to start |
Beta Was this translation helpful? Give feedback.
-
|
@reichowc @faithfull @gaima8 I finally have been able to reproduce this issue. Please see #6429 where I will continue discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm using sharding plugin in RabbitMQ version 3.8.18 without problems, but, when I change to version 3.9.5 the following problem happens: When one node (RabbitMQ) is down, I can't get it up again if I have some policy created.
So, if I delete the policy and try to start the node again, this is possible. Then I need to recreate the policy with the node up to make things work again.
Beta Was this translation helpful? Give feedback.
All reactions