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

TCP layer drop connection state on gap #494

Merged
merged 4 commits into from
Dec 10, 2015

Conversation

urso
Copy link

@urso urso commented Dec 10, 2015

Drop and reinitialize connection state on gap, so application layer parser
will be restarted (after detecting gap).

resolves #342

Drop and reinitialize connection state on gap, so application layer parser
will restarted (after detecting gap).
@urso urso force-pushed the fix/342-pgsql-panic branch from 95130fc to 4f444b5 Compare December 10, 2015 00:46
return TcpStream{}, false
}

timeout := time.Duration(0)
Copy link
Member

Choose a reason for hiding this comment

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

Out of curiosity, is this form preferred over var timeout time.Duration for any technical reasons?

Copy link
Author

Choose a reason for hiding this comment

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

ah, copy'n paste. I'd prefer the 'var timeout time.Duration'. but in this case no big difference

@andrewkroh
Copy link
Member

LGTM

@urso urso added the review label Dec 10, 2015
andrewkroh added a commit that referenced this pull request Dec 10, 2015
TCP layer drop connection state on gap
@andrewkroh andrewkroh merged commit ba6a0f8 into elastic:master Dec 10, 2015
@urso urso deleted the fix/342-pgsql-panic branch January 11, 2016 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

beta4 crashing
2 participants