Closed Victoryship closed 1 year ago
But he is normal when I run the test locally
I try not to use the pipeline in the production environment. Then none of the expireat commands returned as 0. Is it because the order in send is not fixed? The expireat command is executed before the set command?
It is a problem that the redis host of the cloud service provider does not guarantee the order of fragment forwarding
redis_version:3.2.12 redigo: 1.8.9 go version: 1.17 my code `
`
sometims i got expireat command return 0, but err is nil {"level":"ERROR","time":"2023.04.19 18:00:55","message":" set change own limit expire at failed: { 27 0} {key 15 0 im_family_change_owner_status_41380 } {date 11 1681920000 }"}