Highly non-uniform distribution of messages over queue when using UUID as routing key about rabbitmq-consistent-hash-exchange HOT 6 CLOSED

Accidentally posted before fully typing it out. Stand by for more details

from rabbitmq-consistent-hash-exchange.

Ok, all deets are there!

from rabbitmq-consistent-hash-exchange.

Thank you for filing an issue with some evidence.

You are running 3.7.7, so this is already addressed and proven, see #37. Please upgrade to 3.7.14, you are 10 months behind in terms of releases.

We have integration tests that compute and print Chi square values of the final distribution. A quick check suggests they use string values produced from PRNG-derived numbers.

from rabbitmq-consistent-hash-exchange.

Also to be clear, 3.7.7 does not use Jump consistent hashing. That was introduced in 3.7.8, and releaved a few unsafe optimizations in the core that affected this plugin. Those were addressed in subsequent releases and can be found in the change log.

from rabbitmq-consistent-hash-exchange.

Ah, sorry for the version confusion! We will consider upgrading to the later version.

The integration test seems to be using list_to_binary(integer_to_list(rand:uniform(10000000))) to generate data where in my tests I was just doing integer_to_list(rand:uniform(10000)). Using list_to_binary does seem to provide much better distribution. Is that something that'll happen to the routing key?

Thanks for the quick reply!

from rabbitmq-consistent-hash-exchange.

Routing keys parsed from actual protocol frames are always binaries.

from rabbitmq-consistent-hash-exchange.