Hi, In January[1] and June[2] there were discussions regarding the DRAIN state not being preserved when loading server state from file. Looking at the source it looks to me as the issue has not been resolved.
Have you come to a conclusion if the current behaviour is how it will be or if a fix can be expected at some time? My use case is rolling updates where a new version of a web application is started in a Docker container and the previous version (another Docker container) is kept around for its current users with the help of sticky sessions and session draining. I was going to set the backend server of the previous version to state DRAIN, but reloading the configuration later ignores the saved DRAIN state and re-enables the previous version for all users. As discussed previously if I instead set the previous version's backend server weight to 0, it seems to accomplish the requested behaviour and also work across reloads. In my opinion using the DRAIN state would be a more proper way to implement the use case. I need to reload the configuration in order to add the backend server of the new version. I don't think there is a way to add the new server in any other way? [1] https://www.mail-archive.com/[email protected]/msg21347.html [2] https://www.mail-archive.com/[email protected]/msg22982.html Best regards, Thomas
