tree 21b1e9cb4aaf49054d34f07259bea4f27a0dd3b4
parent 413461a9e5225df7f8e201902d6a9cbaba0087c6
author Yunze Xu <xyzinfernity@163.com> 1686039357 +0800
committer GitHub <noreply@github.com> 1686039357 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkfus9CRBK7hj4Ov3rIwAAEu4IAFb2LKpcBYltPkYbFFGaRmcq
 gCCja8ATFgTHSSvUkBEduSp+sottHODb6BYbPLxgIEnqXG/wA4WzUKx3wg/wDUuV
 w8YgTtLJoRjZPKPWfsPErKmRrErWM6SLe7rCtVEgtTKmc8rFqspgC7vnnFdJEwtE
 y/5hN48970ZOQj7RsjPX0hXEI6FMy3f0YtBQHl3tCT1a//xyS/KGUp20YvNsUc7E
 xnnq7ooEvqKpK7HMsCeUnYbyn22bIXuwDb7EZ2WfeJrQ0UsYmXEC6p31DSlhjm2a
 9FvQTnd3IXSC4ubCBbnCuFcFfQ8/3lk6pv3F3DwielyRKWAYivBcsdkKefAuLgE=
 =T6As
 -----END PGP SIGNATURE-----
 

Fix flaky testConsumerEventWithoutPartition cause by the change of Pulsar 3.0 (#281)

### Motivation

https://github.com/apache/pulsar/pull/19502 brings a change to the
consumer selection of the Failover subscription.

Before that PR, if a new consumer joins a Failover subscription when
there is a consumer that subscribes the topic, the new consumer will
receive the "inactive" event.

After that PR, a random consumer will receive the "inactive" event.

### Modifications

Change the assertion when `consumer` subscribes the topic with the same
subscription.

In addition, use a thread safe queue to avoid race conditions.