Hi everyone, I'm trying to understand the exact behavior when

tieredReplicants

is set higher than the number of historicals in a tier. Setup example: • Tier has 3 historicals • Datasource configured with

tieredReplicants: 5

Question: What actually happens in this case? 1. Does Druid cap the replicas at 3 (one per historical)? 2. Can a single historical load multiple copies of the same segment to satisfy the replication factor? 3. Does it fail/warn/queue the additional replicas? I couldn't find explicit documentation about this edge case. The architecture seems designed to distribute segments across different historicals, but I want to confirm the actual behavior when requested replicas exceed available nodes. Has anyone tested this scenario or can point me to the relevant code/docs that clarifies this? Thanks!

Ref: https://apachedruidworkspace.slack.com/archives/C0309C9L90D/p1761885378914639?thread_ts=1761884807.410779&cid=C0309C9L90D