Remove Terracotta Cluster

[Joshua Brodie]

HI Everyone:

Reincarnating an old email thread.

We only use SAML2 for integration to the Univerity's IdP 2.2: we do
not support SAML1.X, WAYF service, or ECP; federation will be by EDS
only & non-federation is with direct integration.

With above criteria, are their any downsides to removing the
terracotta cluster among the three IdP nodes we have running? The load
balancer will remain.

Thanks.

Josh



On 1 March 2012 14:37, Russell Beall <beall at usc.edu> wrote:
> When I need to switch to standalone mode for testing and such, I remove these options from the JAVA_OPTS:
>
>          -Dtc.install-root=/opt/terracotta \
>          -Dtc.config=/opt/terracotta/conf/tc-config.xml \
>          -Xbootclasspath/p:/opt/terracotta/lib/dso-boot/dso-boot-hotspot_linux_160_24.jar"
>
> That is how you would take out session clustering, but as Scott said, you would have to be sure you handle your data requirements so continued operations are not affected by becoming unclustered, (if your plan is to pull away from TC in production as well).
>
> Regards,
> Russ.
>
> On Mar 1, 2012, at 1:58 PM, Joshua Brodie wrote:
>
>> Hi:
>>
>> I am looking after a Shibboleth IdP with terracotta cluster - I am not
>> yet 100% sure how they both work together (~90% sure).
>>
>> If I needed to remove the terracotta cluster, and have just
>> stand-alone IdPs with load-balanced sticky session, is it only to
>> update the 'catalina.sh'? i.e. copmment out the following:
>>
>> "if [ "$1" = "start" ] ; then
>> JAVA_OPTS="-Xmx2048m -XX:MaxPermSize=1024m -XX:+UseParallelOldGC
>> -XX:+DisableExplicitGC \
>>           -Dtc.install-root=/opt/terracotta \
>>           -Dtc.config=/opt/terracotta/conf/tc-config.xml \
>>           -Xbootclasspath/p:/opt/terracotta/lib/dso-boot/dso-boot-hotspot_linux_160_24.jar"
>> fi"
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net