[
https://issues.apache.org/jira/browse/CLOUDSTACK-7841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197232#comment-14197232
]
ASF subversion and git services commented on CLOUDSTACK-7841:
-------------------------------------------------------------
Commit c15ed74f63559dca7692cfcfe695e195c3401454 in cloudstack's branch
refs/heads/4.5 from [~yasker]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c15ed74 ]
CLOUDSTACK-7841: Gracefully reload haproxy config
The old way would disconnect all the existing connections through haproxy when
reload the config.
This new way would ensure that all the existing connections would still alive
after reload the config.
> Existed connections are disconnected when update load balancer configuration
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7841
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7841
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Reporter: Sheng Yang
> Assignee: Sheng Yang
> Fix For: 4.5.0
>
>
> Applying load balancer rules breaks existing connections and causes short
> outage.
> That's because our currently logic of handling haproxy reload configuration
> is not graceful enough, and focused on how to recover from failed newly
> configuration.
> There would be a way to improve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
