geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-2090) Confirm that if version N is deployed, you can distribute version N+1 and later start it somehow
Date Thu, 08 Jun 2006 04:02:29 GMT
Confirm that if version N is deployed, you can distribute version N+1 and later start it somehow
------------------------------------------------------------------------------------------------

         Key: GERONIMO-2090
         URL: http://issues.apache.org/jira/browse/GERONIMO-2090
     Project: Geronimo
        Type: Bug
    Security: public (Regular issues) 
  Components: kernel  
    Versions: 1.1    
    Reporter: Aaron Mulder
     Fix For: 1.1.1


Let's say you deploy foo/MyApp/1.1/war, to 10 identical servers.

Now you have version 1.2 ready.

It would be nice if you could distribute 1.2 to all 10 servers (while 1.1 is still running).
 Then you'd have to be able to run a command to essentially say "switch off 1.1 and switch
on 1.2" in one shot (perhaps using a sticky load balancer to upgrade part of the cluster and
let the rest of the cluster handle old sessions until they're finished).  This isn't precisely
a redeploy (the stuff is already distributed, whereas a redeploy expects to send the new files).
 More of a "cutover" command.

I suspect there may be bugs in the console and/or tool that manifest if you have two different
versions of the same module installed simultaneously.  The deploy tool may also not let you
distribute a second version of the same module.  But we also need a new command to do the
cutover.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message