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

Clarity on error #360

Open
barrct opened this issue Dec 12, 2020 · 0 comments
Open

Clarity on error #360

barrct opened this issue Dec 12, 2020 · 0 comments

Comments

@barrct
Copy link

barrct commented Dec 12, 2020

Simply, I updated the memcached cluster to store more than 1M but I was getting a 1M limit error.

Due to this, I didn't think that the cluster took the setting change and spend a lot of time investigating why the setting didn't take on the server, not realising that there is a default here in the client.

The error was VERY generic being "Error: The length of the value is greater than 1048576". It does say the correct issue but not that the limit is in a setting versus the server.

I would like to suggest that the source of an error have a clear distinction of where the error is (server limit versus client limit).
Maybe something simple like "Error: The length of the value is greater than 1048576, verify that Memcached.config.maxValue matches the server configuration"

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

1 participant