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

Reducing avg Serf UDP packet sizes #967

Merged
merged 1 commit into from
Feb 9, 2016
Merged

Conversation

subnetmarco
Copy link
Member

marshall_event by default now returns an empty object, and the properties to propagate need to be explicitly returned.

This changed the previous behavior where by default marshall_event returned the entire object.

As a result, the average packet size being exchanged by Serf is reduced.

@subnetmarco subnetmarco self-assigned this Feb 8, 2016
@subnetmarco subnetmarco force-pushed the chore/serf-packet-size branch 4 times, most recently from c707c3b to fae2374 Compare February 9, 2016 00:49
@subnetmarco subnetmarco force-pushed the chore/serf-packet-size branch from fae2374 to 41f3448 Compare February 9, 2016 00:59
@subnetmarco subnetmarco added the pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) label Feb 9, 2016
subnetmarco added a commit that referenced this pull request Feb 9, 2016
@subnetmarco subnetmarco merged commit 2d174c4 into next Feb 9, 2016
@subnetmarco subnetmarco deleted the chore/serf-packet-size branch February 9, 2016 01:48
@Tieske
Copy link
Member

Tieske commented Feb 9, 2016

I noticed the docs not being in line with serf docs. Serf has a hard limit of 512 bytes for a custom event. The Kong docs mention 64kb.

@subnetmarco
Copy link
Member Author

@Tieske good catch - we need to update the docs. And also we need to document the change introduced by this PR.

@sonicaghi
Copy link
Member

and streamline the clustering docs.

@subnetmarco
Copy link
Member Author

I have updated the website with the new size limit of 512 bytes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants