Skip to content

Conversation

@jnpkrn
Copy link

@jnpkrn jnpkrn commented May 13, 2016

No description provided.

Previously, the branching used accidentally incorrect (not even
remotely related) condition.

Issue introduced with partial refactoring/rewrite/extension:
9ca5e67
@dmuhamedagic
Copy link

dmuhamedagic commented May 19, 2016 via email

@dmuhamedagic dmuhamedagic merged commit 90fcbc6 into ClusterLabs:master May 19, 2016
@jnpkrn
Copy link
Author

jnpkrn commented May 19, 2016

I rechecked and still think the issue got introduced as detailed in the
commit message. The full packet might always be read thanks to fitting
into a single ethernet frame:

MTU - TCP_HEADER_SIZE > MAX_MSG_LEN
1500 - 60 (upper bound) > 1024

Thanks!

@jnpkrn
Copy link
Author

jnpkrn commented May 19, 2016

(I meant to say that MTU or physical layer for the interconnect in general is pretty much environment specific, and that it used to work reliably is just a matter of typical parameters, such as MTU = 1500/ethernet, dominating in typical deployments.)

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 this pull request may close these issues.

2 participants