Walkthrough

Removes host blacklist tracking and retry control optimization from the line sender. The retry loop now iterates across all hosts without checking prior blacklist state, allowing recovery in dynamic deployment scenarios where host roles change mid-retry.

Changes

Sequence Diagram(s)

sequenceDiagram
    participant Sender
    participant Host A
    participant Host B

    Note over Sender: Before: With Blacklisting
    Sender->>Host A: Send request (fails - non-retryable)
    Note over Sender: Blacklist Host A
    Sender->>Host B: Try Host B
    Host B->>Sender: Reject (read-only)
    Note over Sender: Blacklist Host B<br/>(no hosts available)
    Note over Sender: Wait for retry deadline...<br/>(artificial delay)

    Note over Sender: After: Without Blacklisting
    Sender->>Host A: Send request (fails)
    Sender->>Host B: Try Host B
    Host B->>Sender: Reject (read-only)
    Sender->>Host A: Immediately retry Host A<br/>(no blacklist state)
    Note over Sender: Continues retrying based<br/>on deadline, not blacklist

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify all references to blacklist bitmap and related fields are removed
• Confirm retry loop logic remains intact and functions correctly without blacklist state checks
• Validate that no other code paths depend on the removed blacklist tracking mechanism

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@CodeRabbit review

[PR Coverage check]

😍 pass : 0 / 0 (0%)