-
Notifications
You must be signed in to change notification settings - Fork 596
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
v3.0.2 bytesqueue peak panic #338
Comments
Do you have any way to reproduce it? |
The Panic occurred in the K8S deployment of the production environment. I tried to redeploy it, but there was a persistent Panic. After a brief look at the code location of the Panic, I guess that there is a problem in the key generation. I removed the customized hasher in the NewBigCache configuration, and then recompiled and packaged, then the Panic never appeared. My custom hasher key is uint64, and the definition is as follows:
|
Interesting, what entries and keys looks like? Were the keys randomly distributed? |
Will data skew in a shard cause this problem? Shouldn't it cause a set error rather than a get error, let alone a panic. |
You are right. But maybe this approach will help us debug #283 |
|
found a panic:
Environment:
/etc/os-release
or winver.exe): centosThe text was updated successfully, but these errors were encountered: