You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Warum ist das nicht so? Also in Hunter können wir Appserver gut damit auslasten nicht kompatible Sessions zu deserialisieren und ich denke nicht das das alles initial fails sind sonder auch ganz viele die bis zum nächsten Update der Session im Memcached die letzte Session versuchen zu deserialisieren.
Trying to deserialize sessions that are for some reason not
deserializable leads to continous retries at the moment.
As the data is apparently not loadable, it might be a better idea
to remove the data from memcached alltogether in order to avoid
expensive retries.
For deserialization error this makes sense (you probably would also want to add the session id to the invalidSessionsCache), but not for other issues like a timeout. So this case should be handled more specifically and the session should not be deleted for all exceptions.
Having a test for this would be uber cool! :-)
Trying to deserialize sessions that are for some reason not
deserializable leads to continous retries at the moment.
As the data is apparently not loadable, it might be a better idea
to remove the data from memcached alltogether in order to avoid
expensive retries.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warum ist das nicht so? Also in Hunter können wir Appserver gut damit auslasten nicht kompatible Sessions zu deserialisieren und ich denke nicht das das alles initial fails sind sonder auch ganz viele die bis zum nächsten Update der Session im Memcached die letzte Session versuchen zu deserialisieren.
Trying to deserialize sessions that are for some reason not
deserializable leads to continous retries at the moment.
As the data is apparently not loadable, it might be a better idea
to remove the data from memcached alltogether in order to avoid
expensive retries.