[
https://issues.jboss.org/browse/WFLY-332?page=com.atlassian.jira.plugin.s...
]
rafael liu commented on WFLY-332:
---------------------------------
Also there's have a more specific use case where the user can set a certain
sessionDrainingStrategy value at the moment of the *redeploy*. I think mod_cluster
doesn't support this kind o ad-hoc configuration, but IMO that has some real usages:
1. Suppose sessionDrainingStrategy=DEFAULT/ALWAYS, if there's 1 user hanging (say
doing a huge download) the redeploy will timeout. Even worst, in a N node scenario, there
will be N-1 nodes active during that time.
2. Again with sessionDrainingStrategy=DEFAULT/ALWAYS, if there's a critical bug,
draining may not make sense or may introduce an undesirable delay.
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