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

Allow users to specify conntrack buffer size. #1896

Merged
merged 3 commits into from
Sep 26, 2016
Merged

Conversation

tomwilkie
Copy link
Contributor

So they can work around the ENOBUFFs problems.

@@ -13,6 +13,7 @@ import (
)

const conntrackCloseTag = "</conntrack>\n"
const bufferSize = 1024 * 1024

This comment was marked as abuse.

This comment was marked as abuse.

@@ -152,7 +152,7 @@ func probeMain(flags probeFlags) {
defer dnsSnooper.Stop()
}

endpointReporter := endpoint.NewReporter(hostID, hostName, flags.spyProcs, flags.useConntrack, flags.procEnabled, flags.procRoot, scanner, dnsSnooper)
endpointReporter := endpoint.NewReporter(hostID, hostName, flags.spyProcs, flags.useConntrack, flags.procEnabled, flags.procRoot, flags.conntrackBufferSize, scanner, dnsSnooper)

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@2opremio
Copy link
Contributor

Minor comment/suggestion. Otherwise LGTM

@tomwilkie tomwilkie merged commit b130f1b into master Sep 26, 2016
@tomwilkie tomwilkie deleted the conntrack-buffersize branch September 26, 2016 19:08
@2opremio
Copy link
Contributor

LGTM

@@ -197,6 +199,7 @@ func main() {

// Proc & endpoint
flag.BoolVar(&flags.probe.useConntrack, "probe.conntrack", true, "also use conntrack to track connections")
flag.IntVar(&flags.probe.conntrackBufferSize, "probe.conntrack.buffersize", 208*1024, "conntrack buffer size")

This comment was marked as abuse.

This comment was marked as abuse.

Copy link
Member

@rade rade left a comment

Choose a reason for hiding this comment

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

^

@tomwilkie
Copy link
Contributor Author

Yeah I read it off the Dev cluster and my mini kube VM.

On Monday, 26 September 2016, Matthias Radestock [email protected]
wrote:

@rade commented on this pull request.

In prog/main.go #1896:

@@ -197,6 +199,7 @@ func main() {

// Proc & endpoint
flag.BoolVar(&flags.probe.useConntrack, "probe.conntrack", true, "also use conntrack to track connections")

  • flag.IntVar(&flags.probe.conntrackBufferSize, "probe.conntrack.buffersize", 208*1024, "conntrack buffer size")

looks like that's the default, on some Linuxes at least...

$ cat /proc/sys/net/core/rmem_default
212992


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#1896, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhVMUUqxpgQ8KHebZGRwtabOEqpKUks5quGRSgaJpZM4KG0K2
.

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.

3 participants