[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-1407: -------------------------------- Fix Version/s: 5.2.0.FINAL Affects Version/s: 5.0.0.FINAL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1407: ---------------------------------------- Also, such dynamic update should probably be done in a safe way. For example, before applying the new server list, wait for all requests for the old servers to finish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Manik Surtani reassigned ISPN-1407: ----------------------------------- Assignee: Galder Zamarreño (was: Manik Surtani) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1407: ---------------------------------- Affects Version/s: (was: 5.0.0.FINAL) Priority: Blocker (was: Major) -- 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

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1407: -------------------------------- Fix Version/s: 5.2.0.Beta1 -- 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

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1407: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.2.0.Final) (was: 5.2.0.Beta1) -- 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

[ 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 -- 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

[ https://issues.jboss.org/browse/ISPN-1407?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-1407: ------------------------------------- moved this back to 5.2 - even though it's not *critical* from rolling upgrades not having it impacts the usability significantly (practically require process restart for the clients). -- 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