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

database/gredis: use BRPOP timeout #3669

Open
Lyotoc opened this issue Jun 28, 2024 · 2 comments
Open

database/gredis: use BRPOP timeout #3669

Lyotoc opened this issue Jun 28, 2024 · 2 comments
Labels
bug It is confirmed a bug, but don't worry, we'll handle it.

Comments

@Lyotoc
Copy link

Lyotoc commented Jun 28, 2024

Go version

go1.22.3 linux/amd64

GoFrame version

v2.7.1

Can this bug be reproduced with the latest release?

Option Yes

What did you do?

gredis using redis's BRPOP command reports an error timeout

if msgVars, err := g.Redis.BRPop(ctx, 0, queueName); err != nil {
				logger.Errorf(ctx, "Pull message error %v", err)
				continue
			}

It seems that there is no blocking operation at the bottom layer and the TCP read timeout configured by gredis is applied in this command.

What did you see happen?

Redis Client Do failed with arguments "[BRPop queueName 31536000]": read tcp xx.xx.251.55:11898->10.40.xx.xx:6379: i/o timeout

What did you expect to see?

Normally it should be blocked and the connection should not time out.

@Lyotoc Lyotoc added the bug It is confirmed a bug, but don't worry, we'll handle it. label Jun 28, 2024
@Lyotoc Lyotoc changed the title os/gtime: issue title database/gredis: use BRPOP timeout Jun 28, 2024
@chaseSpace
Copy link

这个怎么看都是 你redis问题

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


No matter how you look at this, it’s all a problem with your redis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It is confirmed a bug, but don't worry, we'll handle it.
Projects
None yet
Development

No branches or pull requests

3 participants