Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis integration not working as expected #356

Open
Ndriw opened this issue Mar 1, 2023 · 2 comments
Open

Redis integration not working as expected #356

Ndriw opened this issue Mar 1, 2023 · 2 comments

Comments

@Ndriw
Copy link

Ndriw commented Mar 1, 2023

Hello,
I've been trying to use redis with the concerto platform by changing the following variables (right now I'm using k8s to host redis):

CONCERTO_SESSION_STORAGE: redis
REDIS_HOST: host
REDIS_PORT: 6379
REDIS_PASS: ''

When I start the test with a new user, a new key is created in redis successfully. However, whenever I refresh the page, while using the same user, a new key is stored in redis rather than using an already existing key.

Using sticky session in place of redis works, but it's not a desirable solution.

Concerto Platform version

5.0.27

Expected behavior

The session should be resumed if it's already present in redis

Actual behavior

A new key is being created in redis and the previous session is not being used

Steps to reproduce the issue

Using the environment variables to start using redis instead of the filesystem, configure the host, port and password, and creating a redis instance, then start a test that uses session.

@tulio-vieira
Copy link

I am also experiencing this issue

@koalawangyang
Copy link

I have the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants