Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Number of relaychain peers isn't limited #1182

Closed
stakeworks opened this issue Jun 16, 2023 · 8 comments · Fixed by #1202
Closed

Number of relaychain peers isn't limited #1182

stakeworks opened this issue Jun 16, 2023 · 8 comments · Fixed by #1202

Comments

@stakeworks
Copy link

stakeworks commented Jun 16, 2023

The max number of relaychain peers should be 40 with default settings:

  --out-peers <COUNT>
      Specify the number of outgoing connections we're trying to maintain
      [default: 8]

  --in-peers <COUNT>
      Maximum number of inbound full nodes peers
      [default: 32]

But this doesn't work, also explicit setting in-peers and out-peers for relaychain doesn't work.

Crab

2023-06-16 10:59:16 [Relaychain] 💤 Idle (413 peers), best: #18379961 (0x6165…ee5b), finalized #18379958 (0x1596…09c7), ⬇ 462.1kiB/s ⬆ 555.8kiB/s

Darwinia

2023-06-16 11:24:47 [Relaychain] 💤 Idle (876 peers), best: #15990958 (0x5a22…075f), finalized #15990956 (0xd094…7afe), ⬇ 118.4kiB/s ⬆ 306.1kiB/s

Ubuntu 20.04.6 LTS & Ubuntu 22.04 LTS
darwinia 6.3.1-unknown =>

@AurevoirXavier
Copy link
Member

What's your boot command?

@stakeworks
Copy link
Author

stakeworks commented Jun 16, 2023

ExecStart=/path/darwinia \
        --collator \
        --chain=crab \
        --base-path /basepath/ \
        --name 'StakeWorks | Crab | CMN02' \
        --execution wasm \
        --prometheus-port port \
        --listen-addr /ip4/xx.xx.xx.xx/tcp/port/ws \
        --listen-addr /ip6/xx:xx:xx:xx::1/tcp/port/ws \
        -- \
        --execution wasm \
        --chain=kusama \
        --base-path /basepath/ \
        --sync=warp \
        --state-pruning 1000 \
        --blocks-pruning 1000 \
        --out-peers 15 \
        --in-peers 35 

The in- and out-peers where added later, but had no effect

@stakeworks
Copy link
Author

Same thing happened with the Interlay Kintsugi chain, after the update to Polkadot 0.9.38

@AurevoirXavier
Copy link
Member

Have you ever encountered this, @fewensa?

@AurevoirXavier
Copy link
Member

Same thing happened with the Interlay Kintsugi chain, after the update to Polkadot 0.9.38

I think there are a lot of light nodes.

Try --in-peers-light 35.

@stakeworks
Copy link
Author

stakeworks commented Jun 24, 2023

I've tried this:

    ... 
    -- \
    --execution wasm \
    --chain=kusama \
    --base-path /basepath/ \
    --sync=warp \
    --state-pruning 1000 \
    --blocks-pruning 1000 \        
    --out-peers 15 \
    --in-peers 35 \
    --in-peers-light 35 \

But after a few minutes I already have over 300 peers.

2023-06-24 09:32:46 [Relaychain] 💤 Idle (309 peers),

@AurevoirXavier
Copy link
Member

AurevoirXavier commented Jun 24, 2023

But after a few minutes I already have over 300 peers.

2023-06-24 09:32:46 [Relaychain] 💤 Idle (309 peers),

There is nothing to do on our end.

Tracking paritytech/cumulus#2563

@AurevoirXavier AurevoirXavier added the U-Won't Fix [Uncategorized] Won't fix. label Jun 24, 2023
@altonen
Copy link

altonen commented Jun 26, 2023

This issue isn't related to light clients. There was a problem in 0.9.40 where the network event stream got clogged and displayed the number of peers incorrectly. This was fixed in 0.9.41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants