Memcached item-size ceiling is startup-only and invisible to protocol clients

Answer

Clients cannot detect a changed item-size ceiling through memcached, and no documented protocol or out-of-band standard advertises it. The ceiling is fixed at startup with -I, so the practical mechanism is to read the process startup flags or deployment configuration and communicate that value to clients outside the protocol. Applications should enforce a client-side payload budget based on the configured limit and treat the server rejection as a deterministic backstop, not the sole enforcement. Splitting or compressing values is optional and should be driven by payload size patterns, not by the protocol.

Confirmed facts

• -I sets the maximum item size at process startup; the default is 1 MB and the value cannot be changed while memcached is running.
• Neither the text nor binary protocol includes a command to query the effective item-size ceiling.
• Store commands above the ceiling are rejected deterministically; the server does not truncate, spill to disk, or accept the same payload on retry.
• Binary-protocol clients receive a numeric status code rather than a text limit value.
• The item-size ceiling and maximum key length are separate limits; -I does not control key length.

Steps for this case

1. Inspect the running process, for example ps -o args= -C memcached, and record the -I value if one is present.
2. Set the client library maximum payload size to that value, or require operators to configure it explicitly for each deployment.
3. Reject oversized values locally before sending them, and map store failures to non-retryable errors when the same payload would exceed the limit.
4. Consider application-level splitting or compression only if values regularly approach the budget; it is an optimization, not a protocol requirement.

Assumptions and uncertainty

This answer assumes the 1 MB default applies only when -I is not specified. If the running value is unknown, the safe client budget is 1 MB; a larger server limit remains unused until the client budget is raised. No documented memcached-native advertisement pattern exists in the research, so out-of-band configuration is presented as the practical approach rather than a standard.

Missing diagnostic detail

The configured -I value for your target deployment. It changes the recommendation because the client budget should match the actual limit instead of defaulting conservatively to 1 MB.

Verification

Start memcached with a known limit such as -I 2m, store a value larger than 1 MB but below 2 MB, and confirm acceptance. Store a value above the configured limit and confirm the command is rejected without partial data. Determine the effective value from the process command line, not from a protocol command.