Recommendation on Ticket Storage

[Wickham, Jeremy]

We have been users of the Memcached Ticket Registry for a few years now (Current Production CAS is v4.0.4). I am currently looking to upgrade our CAS implementation to v5.0.x and when implementing the memcached registry in my test environment, I am getting a lot of inconsistences that do not resonate well with me. I’ve polled this mailing list and there hasn’t been any response on the errors I’m receiving. That means I’m looking towards another avenue on our ticket storage. We have 4 CAS nodes, so a shared or replication instance must be used.

 

I’m curious to know what you are currently using and why does it work for your implementation?

 

Cheers,

 -Jeremy

 

________________________

Jeremy Wickham

Senior Systems Analyst

Mississippi State University

jeremy....@msstate.edu

 

[RJ Guroo]

Hazelcast seems to be doing great with CAS. We are also working on getting this working.

--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/46776a85ab1041d18dccaa87203a3494%40mail04.ad.msstate.edu.

[Wickham, Jeremy]

Thank you for your response. This is the registry I am looking at right now.

 

Cheers,

 -Jeremy

 

From: cas-...@apereo.org [mailto:cas-...@apereo.org] On Behalf Of RJ Guroo
Sent: Tuesday, March 07, 2017 9:17 AM
To: cas-...@apereo.org
Subject: Re: [cas-user] Recommendation on Ticket Storage

 

Hazelcast seems to be doing great with CAS. We are also working on getting this working.

On Mon, Mar 6, 2017 at 2:30 PM, Wickham, Jeremy <jeremy....@msstate.edu> wrote:

We have been users of the Memcached Ticket Registry for a few years now (Current Production CAS is v4.0.4). I am currently looking to upgrade our CAS implementation to v5.0.x and when implementing the memcached registry in my test environment, I am getting a lot of inconsistences that do not resonate well with me. I’ve polled this mailing list and there hasn’t been any response on the errors I’m receiving. That means I’m looking towards another avenue on our ticket storage. We have 4 CAS nodes, so a shared or replication instance must be used.

 

I’m curious to know what you are currently using and why does it work for your implementation?

 

Cheers,

 -Jeremy

 

________________________

Jeremy Wickham

Senior Systems Analyst

Mississippi State University

jeremy....@msstate.edu

 

--

- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/46776a85ab1041d18dccaa87203a3494%40mail04.ad.msstate.edu.

 

--

- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CACNfiM%2BhSNjMe%2B2WZK3c2h8-5a2wQQJt82HoWSW2Po4co6yG1w%40mail.gmail.com.