~titusx/nginx/module-upstream-fair : changes

~titusx/nginx/module-upstream-fair » Changes from revision 64

From Revision 64 to 45

Rev	Summary	Authors	Date
64	Merge pull request #8 from mikegagnon/master Merge pull request #8 from mikegagnon/master fixed off-by-one bug in the calculation of shm_name->len	Grzegorz Nosek	12 years ago
63	Merge pull request #4 from pkwarren/issue3 Merge pull request #4 from pkwarren/issue3 Fix building against nginx without the --with-debug option specified.	Grzegorz Nosek	12 years ago
62	Merge pull request #2 from qualtrics/master Merge pull request #2 from qualtrics/master Fixed a bug ngx_http_upstream_fair_sched_score function.	Grzegorz Nosek	12 years ago
61	Fix best_sched_score initialisation on 64-bit architectures Fix best_sched_score initialisation on 64-bit architectures Thanks to Victor Lavrenko for reporting, analysing and providing a patch.	Grzegorz Nosek	14 years ago
60	Silly logic bug in idle/no_rr mode checking Silly logic bug in idle/no_rr mode checking Yay for De Morgan's laws.	Grzegorz Nosek	15 years ago
59	upstream_fair has a home page! Update README upstream_fair has a home page! Update README	Grzegorz Nosek	15 years ago
58	Status handler improvements and fixes Status handler improvements and fixes	Grzegorz Nosek	15 years ago
57	Replace per-worker refcount with a concurrent request counte... Replace per-worker refcount with a concurrent request counter	Grzegorz Nosek	15 years ago
56	Keep our own generation counter instead of relying on ngx_cy... Keep our own generation counter instead of relying on ngx_cycle	Grzegorz Nosek	15 years ago
55	Don't store pointers inside the shm segment at all Don't store pointers inside the shm segment at all (an exceptional use-case is the status handler but it takes care to do things safely)	Grzegorz Nosek	15 years ago
54	Use ngx_cycle instead of various tricks to store the current... Use ngx_cycle instead of various tricks to store the current cycle somewhere	Grzegorz Nosek	15 years ago
53	Fix (another) crash in status display after reload Fix (another) crash in status display after reload	Grzegorz Nosek	15 years ago
52	Debug message tweaks Debug message tweaks	Grzegorz Nosek	15 years ago
51	weight_mode=(idle\|peak) parameter support weight_mode=(idle\|peak) parameter support Weight mode 'idle' means that a backend is considered idle when servicing less than 'weight' requests. This has special meaning when running in no_rr mode. The backends are chosen from the following groups with descending priority: - backends with 1 <= nreq <= weight (by descending nreq) - totally idle backends - all other (busy) backends This mode (idle+no_rr) is particularly suited to small setups with backends started on demand. It requires care in bigger installations, as it may overload a range of backends without ever using others. Weight mode 'peak' means that no backend may serve more than 'weight' requests at once. Once this limit is reached, nginx starts to return 502 errors. This is useful when you want to limit the load on your backends at the price of errors sent to the client (although this might be an advantage in e.g. tiered load balancer setups). So the distinct modes of upstream_fair operation are: * default * no_rr * no_rr weight_mode=idle * weight_mode=peak All other combinations are more or less pointless, at least for now.	Grzegorz Nosek	15 years ago
50	Replace atomic ops with normal ones (except the spinlock, of... Replace atomic ops with normal ones (except the spinlock, of course)	Grzegorz Nosek	15 years ago
49	Fix status report for multiple fair upstreams Fix status report for multiple fair upstreams	Grzegorz Nosek	15 years ago
48	Use per-upstream spinlock to protect access to shared memory Use per-upstream spinlock to protect access to shared memory	Grzegorz Nosek	15 years ago
47	Fix crash in status handler if called right after reload Fix crash in status handler if called right after reload	Grzegorz Nosek	15 years ago
46	Use monotonic request counter instead of time data, track to... Use monotonic request counter instead of time data, track total number of requests per upstream and per backend	Grzegorz Nosek	15 years ago
45	The `fair' directive now takes parameters. The `fair' directive now takes parameters. Currently the only parameter is `no-rr' which disables round-robin behaviour, i.e. if you only need X backends to keep up with your peak load, backends X+1 should never receive any requests. Note that this does make the load balancer unfair as requests are definitely not distributed evenly.	Grzegorz Nosek	15 years ago

Older »