Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Most close ephemeral peers or leak peer objects #817

Merged
merged 4 commits into from
Jul 1, 2015
Merged

Conversation

Raynos
Copy link
Contributor

@Raynos Raynos commented Jul 1, 2015

We were leaking peer objects in prod; peer objects will
report stats in a loop. Because we 10s of thousands of
these objects we were reporting the same stat 10s of
thousands of time and saw a huge spike in about 5k
UDP writes per second.

r: @rf @jcorbin @kriskowal

var peer = self.channel.peers.get(self.socketRemoteAddr);
if (peer) {
peer.close(noop);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great and fits our immediate need, but you might be able to knock a non-ephemeral peer out by issuing an ephemeral request from it.

@kriskowal
Copy link
Contributor

🆗

@rf
Copy link
Contributor

rf commented Jul 1, 2015

lgtm

Raynos added a commit that referenced this pull request Jul 1, 2015
Most close ephemeral peers or leak peer objects
@Raynos Raynos merged commit 26e758d into master Jul 1, 2015
@Raynos Raynos deleted the close-ephemeral-peer branch July 1, 2015 20:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants