clustering with HazelcastStorageService
cantor.2 at osu.edu
Thu Apr 28 09:49:53 EDT 2016
> > Hmm, I would have thought the session cache would have instantiated one
> > instance of a storage engine for the entire idp, but it sounds like
> > you're saying it actually instantiates an instance for each individual
> > session? Or am I misunderstanding? I'm not quite sure what you mean by
I don't know what you mean, actually. I said "context", not storage engine. The storage plugins implement a Java interface, and so a bean of that type is the "engine" in the IdP. The context/key split is just a two part key to allow for co-habitation within one storage instance by different storage clients, and the context is just a string.
The session cache happens to store its data by using random context names that are derived from the session ID it's storing.
Most of the other cases tend to pick a context like "_replay" to store records under.
> Yep, I took a peek through the code and it does look like that's the
> case, each idp session creates a new separate instance of the storage
> backend just for the data needed for that session.
I don't really know what you mean by separate instance.
More information about the users