From ad2dc562af968b9ec8fa30d58604d383a9a64851 Mon Sep 17 00:00:00 2001 From: Murali Reddy Date: Tue, 25 Sep 2018 14:54:17 +0530 Subject: [PATCH 1/2] document connection limit Fixes #3395 --- site/concepts/network-topology.md | 7 +++++++ site/kubernetes/kube-addon.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/site/concepts/network-topology.md b/site/concepts/network-topology.md index 111dd453..2b7e3804 100644 --- a/site/concepts/network-topology.md +++ b/site/concepts/network-topology.md @@ -142,6 +142,13 @@ is not reachable, then the packet is dropped. For most protocols (for example, TCP), the transmission will be retried a short time later, by which time the topology should have updated. +#### connection limit + +In a fully connected mesh of N peers, this would mean N^2 connections. To constrain the resource consumption and +communication between the peers and complexity of route calculation there is a configurable upper limit on the +maximum number of connections that a peer can make to the remote peers. There is safe default value (100) which works +for most deployment. However if you would like to increase the number of peers, you should be able to explicitly override the +default value by setting the CONN_LIMIT environment variable or explicitly invoking weave launch like `weave launch --connlimit=100`. **See Also** diff --git a/site/kubernetes/kube-addon.md b/site/kubernetes/kube-addon.md index 56889e12..4e585cee 100644 --- a/site/kubernetes/kube-addon.md +++ b/site/kubernetes/kube-addon.md @@ -376,7 +376,7 @@ The list of variables you can set is: * `CHECKPOINT_DISABLE` - if set to 1, disable checking for new Weave Net versions (default is blank, i.e. check is enabled) * `CONN_LIMIT` - soft limit on the number of connections between - peers. Defaults to 30. + peers. Defaults to 100. * `HAIRPIN_MODE` - Weave Net defaults to enabling hairpin on the bridge side of the `veth` pair for containers attached. If you need to disable hairpin, e.g. your kernel is one of those that can panic if hairpin is enabled, then you can disable it From f82440f792b8f5cf6eda08e87d00ec922b988828 Mon Sep 17 00:00:00 2001 From: Murali Reddy Date: Wed, 5 Dec 2018 16:14:41 +0530 Subject: [PATCH 2/2] modification to reflect CONN_LIMIT only for Kubernetes --- site/concepts/network-topology.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/site/concepts/network-topology.md b/site/concepts/network-topology.md index 2b7e3804..6153224a 100644 --- a/site/concepts/network-topology.md +++ b/site/concepts/network-topology.md @@ -142,13 +142,15 @@ is not reachable, then the packet is dropped. For most protocols (for example, TCP), the transmission will be retried a short time later, by which time the topology should have updated. -#### connection limit +#### Connection Limit In a fully connected mesh of N peers, this would mean N^2 connections. To constrain the resource consumption and communication between the peers and complexity of route calculation there is a configurable upper limit on the maximum number of connections that a peer can make to the remote peers. There is safe default value (100) which works for most deployment. However if you would like to increase the number of peers, you should be able to explicitly override the -default value by setting the CONN_LIMIT environment variable or explicitly invoking weave launch like `weave launch --connlimit=100`. +default value by passing the value through `connlimit` flag for e.g.`weave launch --connlimit=100`. If you are using Weave with +Kubernetes using [Kubernetes Addon](/site/kubernetes/kube-addon.md) then you can set CONN_LIMIT environment variable to set +the connection limit. **See Also**