On 12/14/2012 11:32 AM,
helpdesk....@gmail.com wrote:
>
> This is a recurring case, I am trying to figure which way would be
> better for us.
>
> 1) Would it be ok if we deleted the session object from memcached by
> using the session-manager generated key?
You have to remove all items from memcacheds that are related to the
session. Run memcached with -vv to see which keys are stored for a
session (on primary node and backup node, which is the "next" from the
node ring) to find out how keys are generated (e.g. some with "bak:" and
"validity:" prefixes). Sorry I don't have the time to find out exact
details for you right now.
> 2) Would you please give us some directions for how to add this logic
> into msm?
Check out MemcachedBackupSessionManager (in tc6/tc7 modules), there are
remove methods for a Session. There you would add some method to
invalidate a session by id. The method might already exposed via jmx
automatically, just check this.
Implement your changes in a github branch so that I can review/support.
Cheers,
Martin
>
> Thanks again.
>
>
> 14 Aralık 2012 Cuma 11:49:13 UTC+2 tarihinde Martin Grotzke yazdı:
>
> Is this a one-time action or is this a recurring use case?
>
> For 1) I'd suggest to manually delete items related to the session from
> memcached, for 2) this could be built into msm e.g. in combination with
> a jmx interface (that could be exposed via some more user friendly
> ui if
> necessary).
>
> Cheers,
> Martin
>
>
> On 12/14/2012 10:03 AM,
helpdesk....@gmail.com <javascript:> wrote:
> > Hi,
> >
> > Our website admins would like to be able to expire someone's session
> > immediately. What is the suggested way doing this in a multi-server
> > environment using non-sticky sessions?
> >
> > Thanks.
> >
> >
>
--
inoio gmbh -
http://inoio.de
Breitenfelder Str. 13c, 20251 Hamburg
Amtsgericht Hamburg, HRB 123031
Geschäftsführer: Dennis Brakhane, Martin Grotzke, Ole Langbehn