Skip to content

manager: Prioritize public addresses for dialing #527

@lexnv

Description

@lexnv

The transport manager takes 8 addresses from the address store of a peer during the dialing process:

We have seen cases on Paseo where validators are behind NATs that produce 31 addresses, most of them being private and unreachable.

The transport manager sorts addresses by score, however:

To ensure we are reaching the peer and not wasting resources (and introducing connectivity delays specifically for elastic scaling), we can prioritize addresses by public/private for the address store sorting criteria. This ensures that public addresses are at the head of the list as long as they are reachable.

Part of:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions