Terracotta

[Christopher Bongaarts]

Another option would be to run in a failover-only mode instead of load 
balancing (i.e "active-passive" instead of "active-active"), and accept 
that failing over will effectively clear IdP state.  If your current 
server is handling the load fine and you're just looking to minimize 
downtime in the event of a problem, you could do it this way.

On 10/11/2012 2:11 PM, Russell Beall wrote:
[...]
> Because of this and issues with high load, Terracotta is not necessarily
> the ideal choice.
[...]
> On Oct 11, 2012, at 12:45 AM, Baird-Parker, David wrote:
>
>> Hi everyone,
>> now that we have an IdP back up and running we ideally want to have a
>> second machine.  Naively, I thought it would just be a case of adding
>> a second server and load balancing which works to a point but logins
>> fail on server 2.  I’ve been advised by the UK Fed to follow the
>> instructions
>> athttps://wiki.shibboleth.net/confluence/display/SHIB2/IdPCluster
>> However,those instructions are for Terracotta 3.2.1 and the current
>> version is 3.7.0 available
>> fromhttp://terracotta.org/downloads/open-source/catalog
>> and as I’ve got Windows servers what would have been available as an
>> exe file now only seems to be available as a jar file so I’m thinking
>> a lot could go wrong if I try to apply the previous instructions to
>> the new version.
>> Has anyone got experience with this version of Terracotta?  If so,
>> what did you do differently to previous versions and how well does it
>> work.  If you’ve used something else to make multiple IdP’s work
>> together that you think might serve us better I’d like to know about
>> that too before starting on this.
>> Any help would be appreciated.
>> Thanks,
>> David

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%