Awesome. I'm looking forward to using some of these new features, especially the ability to set a server's weight to 0.
--Bryan On Mon, Jul 27, 2009 at 5:48 PM, Willy Tarreau<[email protected]> wrote: > Hi all, > > I got several annoying bug reports which all finally got fixed > (last one fixed this evening). So, since the bug queue is now > empty, it's a good time to release a new version. > > I now encourage everyone to migrate to maintenance release 1.3.19. > The 3 last bugs I fixed can cause random pauses in traffic and > sometimes return 502 server error for extremely small objects if > the server closes too fast. This should be enough to motivate you > to upgrade. > > The less nasty one (server error) also affected old versions > such as 1.3.15 and 1.3.14, so I have released one of each as > well. > > But now let's talk about the goodies. Having a development > tree in parallel is nice, because it allows better testing > with less risks, and the ability to backport riskless features. > > So there are a few minor features that I have backported > since there is some demand : > > - support for multiple configuration files. You can now have > up to 10 files in which you split your various sections > (eg: global, http defaults, http frontends, http backends, > tcp frontends, tcp backends). > > - a lot more verbose error reporting when checking the conf, > even if you specify "-D". I have encountered huge errors > in some configurations which were not detected, so some > specific checks have been added for such errors, and the > config parser now returns after reporting all the errors, > not only the first one. This helps for instance when checking > a config which has hostnames which do not resolve where you > check it. > > - support for per-server source port ranges, because there > are some people who needed to overcome the 64k concurrent > connections limit (!) They promised to send me a screenshot > of their stats page when they reach the million if ever :-) > > - support for setting a server's weight to zero, which helps > for maintenance periods. It's better than setting it backup > as you're certain it will never be used for new requests, > even if it's alone. > > And that's all for the features, so that's pretty minimal as > you can see. The goal of this maintenance release clearly is > to be a bugfix release before anything else. > > The develpment version has much more interesting things, but > I've not released it yet as I need to fix my release scripts > first, which are getting really annoying to use. I will send > a new mail for this one. > > This time there is no sparc binary because I have not yet > unpacked my Ultra5 since I moved. I hope to do so quite soon, > but no ETA is set yet. If someone really needs the sparc > binary, please tell me and I may find the courage to plug > it just for the time to build. > > Source, changelog and Linux/x86 binary for 1.3.19, 1.3.15.10 > and 1.3.14.14 are here as usual : > > http://haproxy.1wt.eu/download/1.3/ > > BTW, some of you might have noticed that the GIT interface > work much better now. I've replaced the server. The 25 MHz > HP was replaced with a 500 MHz mini-PC :-) > > Special note to the distro packagers : as usual, wait a few > days in case something very big would be discovered, and please > update your packages, as the bugs described above are really > nasty to chase and describe for the end user. > > Happy upgrade, > Willy > > >
