[fix][broker] Streaming dispatcher stuck after reading the first entry with SHARED subscriptions

[nicoloboschi]

NOTE: THIS BUG IS NOT IN ANY RELEASED VERSION OF PULSAR.

Motivation

While using a streaming dispatcher (streamingDispatch=true), the consumer (with a shared subscription) is stuck and it's not able to fully read a topic. That is because after the an entry is read, the readMoreEntries method is not triggered anymore. This is a regression introduced in #16968

Modifications

• Aligned the new usage of the method sendMessagesToConsumers in the PersistentStreamingDispatcherMultipleConsumers in the same way it's used in PersistentDispatcherMultipleConsumers
• Implemented the option DispatcherDispatchMessagesInSubscriptionThread also in the streaming dispatcher - this might be done in another pull but it's a very tiny change - follow up of [enh] Broker - Shared subscription: run filters in a separate (per-subscription) thread (dispatcherDispatchMessagesInSubscriptionThread) #16603

The evidence of this bug is that the test a several tests with streaming enabled are failing but since they are in the flaky section, they have been ignored. Now these tests are passing

• doc-not-needed

[eolivelli]

great catch !

[mattisonchao]

Hi @nicoloboschi
I'm sorry for missing the PersistentStreamingDispatcherMultipleConsumers. And thanks to your point out.

It looks like it just affects 2.11 and master. Because of the previous branch, we use this PR https://github.com/apache/pulsar/pull/17053/files to cherry-pick.

Another concern is why we don't have the test to verify it. :(

[mattisonchao]

Nice catch, and thanks to you!

[mattisonchao]

I will try to move the StreamingDispather relative test out of the flaky group. Plus, I will remove the label release/2.8.5, release/2.9.4 and release/2.10.2 because we don't need to cherry-pick.