Description:
When cross-region hedging is enabled on a single-master account, the hub region processing header (x-ms-cosmos-hub-region-processing-only) is not carried over to hedged requests. Currently, if a read
request hits 404/1002 twice, the SDK correctly determines that hub region processing is needed and attaches the header on retry. But when a hedged request is dispatched in parallel, it starts with a clean
slate and has no awareness of this decision. This can lead to hedge requests getting successful responses from non-hub region as well which will not help in scenarios with LastCommittedWriteRegion read consistency strategy.
Description:
When cross-region hedging is enabled on a single-master account, the hub region processing header (x-ms-cosmos-hub-region-processing-only) is not carried over to hedged requests. Currently, if a read
request hits 404/1002 twice, the SDK correctly determines that hub region processing is needed and attaches the header on retry. But when a hedged request is dispatched in parallel, it starts with a clean
slate and has no awareness of this decision. This can lead to hedge requests getting successful responses from non-hub region as well which will not help in scenarios with LastCommittedWriteRegion read consistency strategy.