-
Notifications
You must be signed in to change notification settings - Fork 578
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
Error logs about bytes allocation? #348
Labels
Comments
It's generated by this line Line 138 in 16df11e
and we are using logger from stdlib that prints to stderr so technically it's not an error as there are no severity/levels in stdlib (although there could be in the future Go proposal: structured logging). If you see it often you can disable verbose or increase size to one mentioned in last log you see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue you are having?
I'm seeing this get printed out with a severity of
error
. I'm wondering is this something I need to worry about? If not, is there a reason why it reports as anerror
vs. ainfo
orwarn
?I'm basically using the default configuration but
I'm wondering is there a guide lines on how to properly configure the shards properly? Also sorry if this isn't the right forum to ask the question. I can move it somewhere else if you know a better forum for this quesiton.
Environment:
github.com/allegro/bigcache v1.2.1
go 1.18
The text was updated successfully, but these errors were encountered: