-
Notifications
You must be signed in to change notification settings - Fork 275
Description
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"