summaryrefslogtreecommitdiff
path: root/t/maxconns.t
diff options
context:
space:
mode:
authordormando <dormando@rydia.net>2011-09-27 17:42:35 -0700
committerdormando <dormando@rydia.net>2011-09-27 17:52:07 -0700
commitd1f9d992ce722e01d981f8baec9c9ce4e0d2e7c6 (patch)
tree78a3d264e99dd778777df9d3c6bf7a27cd8bd0ed /t/maxconns.t
parentaadd4a098deeb29504a7e482673b32c9bb3e114a (diff)
downloadmemcached-d1f9d992ce722e01d981f8baec9c9ce4e0d2e7c6.tar.gz
experimental maxconns_fast option
Also fixes -c option to allow reducing the maximum connection limit. This gives a new option "-o maxconns_fast", which changes how memcached handles hitting the maximum connection limit. By default, it disables the accept listener and new connections will wait in the listen queue. With maxconns_fast enabled, new connections over the limited have an error written to them and are immediately closed by the listener thread. This is currently experimental, as we aren't sure how clients will handle the change. It may become the default in the future.
Diffstat (limited to 't/maxconns.t')
-rwxr-xr-xt/maxconns.t4
1 files changed, 3 insertions, 1 deletions
diff --git a/t/maxconns.t b/t/maxconns.t
index d30966a..14b5eae 100755
--- a/t/maxconns.t
+++ b/t/maxconns.t
@@ -1,4 +1,6 @@
#!/usr/bin/perl
+# NOTE: This test never worked. Memcached would ignore maxconns requests lower
+# than the current ulimit. Test needs to be updated.
use strict;
use warnings;
@@ -11,7 +13,7 @@ use MemcachedTest;
# start up a server with 10 maximum connections
-my $server = new_memcached('-c 10');
+my $server = new_memcached('-c 100');
my $sock = $server->sock;
my @sockets;