[
https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1407:
-------------------------------------
So this functionality is needed in order to switch the HR clients connected to cluster A
(running e.g. ISPN 5.2) to cluster B (running e.g. ISPN 5.3) when doing rolling
upgrades.
This involves an sys admin connecting to every client and manually updating this list.
What I'm suggesting is a potentially more elegant approach to achieve this, by
upgrading the HR protocol:
- sys admin connects(JMX) to cluster A and marks the site as "upgraded to cluster
B"
- at this stage the HR endpoints on cluster A, when receiving requests from connected
users, would also tell them(piggyback, same as we do with topology info) to connect to
"cluster B" on next requests
- this way the sys admin does not have to update the list of servers for all the users
(there might be lots of them), but only update it once on the server side
Make sure the server_list attribute of the Hot Rod Client can be
updated dynamically
------------------------------------------------------------------------------------
Key: ISPN-1407
URL:
https://issues.jboss.org/browse/ISPN-1407
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Sanne Grinovero
Assignee: Galder ZamarreƱo
Fix For: 6.0.0.Final
when starting a rolling upgrade it will be needed to upgrade the server_lists with new
entries at the start of the upgrade, and possibly remove some entries when the upgrade is
done
--
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