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

Don't every store NEW conntrack flows (only every store updates). #1541

Merged
merged 1 commit into from
May 27, 2016

Conversation

tomwilkie
Copy link
Contributor

This closes a small window where we might produce reports which contain flows that are NEW but have never seen an UPDATE, which can potentially be invalid.

This closes a small window where we might produce reports which contain flows that are NEW but have never seen an UPDATE, which can potentially be invalid.
@2opremio
Copy link
Contributor

which can potentially be invalid.

When would this happen? Aren't there any situations in which we would want to track NEW flows with no UPDATES?

@tomwilkie
Copy link
Contributor Author

When would this happen? Aren't there any situations in which we would want to track NEW flows with no UPDATES?

TBH I don't know; I just observed in #1466 that all invalid flows fit the criteria of "they never saw an update". This PR is an extension of #1466, to catch a small window where we might include flows which never saw an update.

I don't know for sure that all NEW flows which have never seen an UPDATE are invalid. But this certainly made a big difference to the topology.

@tomwilkie
Copy link
Contributor Author

Worth adding that all 'good' flows I've observed see an UPDATE almost immediately after a NEW, so I'm not particularly worries about missing flow.

@2opremio
Copy link
Contributor

OK, then LGTM

@tomwilkie tomwilkie merged commit 277bd70 into master May 27, 2016
@tomwilkie tomwilkie deleted the conntrack-race branch May 27, 2016 10:25
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