[
https://issues.jboss.org/browse/WFLY-332?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on WFLY-332:
-------------------------------------
Rafael, if I understand correctly, you are saying that having session-draining-strategy
configuration separately for undeploy and redeploy would make sense?
I am somewhat failing to see how. In case #1, the redeployment should not fail, the
session just won't be drained in time, then the app will be redeployed. While at it,
in such use case, one would use e.g. mod_cluster manager to draing the sessions manually
in order to prevent termination of a very long running requests. Those are not common
though. Also, there is always n-1 when the app is undeployed. In case #2, you would
upgrade whole cluster immediately and won't perform any session draining.
Add sessionDrainingStrategy configuration option to modcluster
subsystem
------------------------------------------------------------------------
Key: WFLY-332
URL:
https://issues.jboss.org/browse/WFLY-332
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Fix For: 8.0.0.Beta1
Add sessionDrainingStrategy configuration option to modcluster subsystem
* xsd 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira