Partition request does not return extra partitions

[ThorbenLindhauer]

Topic creation as a retry mechanism which can lead to the situation where a requested topic with x partitions is created with more than x partitions. In this case, the partition request implemented in #530 returns only x partitions. Similar behavior occurs in the case of deployments, i.e. a deployment is only distributed to x partitions.

Reason: Both endpoints rely on collecting all the created partitions. This currently only respects the first x partition CREATED events on the system log.

[menski]

This means if we deploy a workflow on a topic which has retry partitions the deployment is successful but the workflow does not exist on all partition of the topic? So the client will fail to start workflow instances while doing round robin as the topology also contains retry partitions? Is that correct?

[ThorbenLindhauer]

Yes, correct.

[menski]

Okay thanks for confirmation then I think we should address that in the near future after finishing our current topics.

[ThorbenLindhauer]

Here's a test for the partition request: e619691#diff-7bb9375e8ef161a823e4fe842066351dR123