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

Implement a blacklisting mechanism for libp2p peers #35

Open
richard-ramos opened this issue May 8, 2019 · 0 comments
Open

Implement a blacklisting mechanism for libp2p peers #35

richard-ramos opened this issue May 8, 2019 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@richard-ramos
Copy link
Member

Some peers are causing an increase in CPU usage when they connect/disconnect. I have identified two of them which spiked the processor to 100%.

if(peer.id.toB58String() !== "QmNo4aCrDJkwg7V1t28kp6EehNVYX3DkTa2UAdi9UaS4Vw" ||

Implement a blacklisting mechanism that after N reconnect attempts in a period of time, will stop murmur from invoking: this.node.dial(peer, () => { });.

@richard-ramos richard-ramos added bug Something isn't working enhancement New feature or request labels May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant