The health checks work the same as for a general backend. The worse the health of
an individual server within a balanced backend, the less likely it will be to get new
connections.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1940 d4fa192b-c00b-0410-8231-f00ffab90ce4

* Removed -n switch from varnish defaults file and varnishlog init script.
  Use the default instance name instead.  This makes sure varnish utilities work
  without having to use the -n switch for the default instance.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1935 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1934 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1933 d4fa192b-c00b-0410-8231-f00ffab90ce4

and very basic, but it should be ready for testing. Two strategies for load balancing
are implemented: a simple round robin, and a simple weighted random. The following
is an example configuration in vcl. The weight parameter for random is optional. Default
is equal weight.

backend foo {
	set backend.host = "foo.bar.com";
	set backend.port = "http";
}

backend_round_robin rr {
	set backend.set = {
		{ "foo1.bar.com", "http" }
		{ "foo2.bar.com", "http" }
		{ "foo3.bar.com", "http" }
	};
}

backend_random rrr {
	set backend.set = {
		{ "foo1.bar.com", "http", 0.3 }
		{ "foo2.bar.com", "http", 0.6 }
		{ "foo3.bar.com", "http", 0.1 }
	};
}

sub vcl_recv {
	if {req.http.host ~ "foo"} {
		req.backend = foo;
	} elseif {req.http.host ~ "bar"} {
		req.backend = rr;
	} else {
		req.backend = rrr;
	}
}




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1931 d4fa192b-c00b-0410-8231-f00ffab90ce4

a Host: header.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1930 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1928 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1927 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1926 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1925 d4fa192b-c00b-0410-8231-f00ffab90ce4

in ticket #144.

Use per backend mutex, do refcounts right, protect the address structures
with a sequence number.

Should close #144.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1919 d4fa192b-c00b-0410-8231-f00ffab90ce4

handling.

Add more asserts.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1918 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1917 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1916 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1915 d4fa192b-c00b-0410-8231-f00ffab90ce4

unlucky multiple times in which case the responsibility falls back to
cnt_lookup().

Fixes 144.





git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1913 d4fa192b-c00b-0410-8231-f00ffab90ce4

WikiText from a change log.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1912 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1909 d4fa192b-c00b-0410-8231-f00ffab90ce4

add an explicit dependency so the logs are regenerated if the stylesheet
changes.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1907 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1905 d4fa192b-c00b-0410-8231-f00ffab90ce4

DocBook, and that I don't have <filename>, <literal>, <varname> etc. -
just <code>.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1904 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1903 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1902 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1898 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1896 d4fa192b-c00b-0410-8231-f00ffab90ce4

Move the VRT initializer for simple backends home.

Add a backend method to get hostname.  This may be a hack.

Move fields private to "simple" to its private structure.

Add cleanup method to backend, so we can collect the garbage.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1895 d4fa192b-c00b-0410-8231-f00ffab90ce4

when a new VCL instantiates a backend.

Drop backends when their reference count goes to zero.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1894 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1893 d4fa192b-c00b-0410-8231-f00ffab90ce4

For now all we have is a "simple" method, but we want more complex
methods later on, round-robin, least-busy and so on.

For now, fall into the other ditch and move everything to 
cache_backend_simple.c, we will move bits back as the gain generality.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1892 d4fa192b-c00b-0410-8231-f00ffab90ce4

a couple of now pointless debugging messages in pipe mode.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1889 d4fa192b-c00b-0410-8231-f00ffab90ce4

across unchanged, otherwise the semantics of the Connection: header cannot
be interpreted correctly by the server.

wget(1) could trigger this problem and would have to wait for the server
to close the (seemingly idle) connection before continuing.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1888 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1886 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1885 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1884 d4fa192b-c00b-0410-8231-f00ffab90ce4

It's a fine point of C-linguistics, but I have to admit that in
certain universes it would have a point.  Not this one though.




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1883 d4fa192b-c00b-0410-8231-f00ffab90ce4

code that invokes it.

If fmtcheck(3) is available, we refuse pedal target practice.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1882 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1881 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1880 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1877 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@1875 d4fa192b-c00b-0410-8231-f00ffab90ce4