WARNING: Version 1.5 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Deprecated in 1.5.0.
The memcached transport is deprecated and will be removed in 2.0.0
The memcached module allows to expose elasticsearch APIs over the memcached protocol (as closely as possible).
It is provided as a plugin called
transport-memcached and installing
. Another option is to download the memcached plugin and placing it
The memcached protocol supports both the binary and the text protocol, automatically detecting the correct one to use.
Memcached commands are mapped to REST and handled by the same generic REST layer in elasticsearch. Here is a list of the memcached commands supported:
GET command maps to a REST
GET. The key used is the
URI (with parameters). The main downside is the fact that the memcached
GET does not allow body in the request (and
SET does not allow to
return a result…). For this reason, most REST APIs (like search) allow
to accept the "source" as a URI parameter as well.
SET command maps to a REST
POST. The key used is the
URI (with parameters), and the body maps to the REST body.
DELETE command maps to a REST
DELETE. The key used is
the URI (with parameters).
QUIT command is supported and disconnects the client.
The following are the settings the can be configured for memcached:
A bind port range. Defaults to
It also uses the common network settings.
The memcached module can be completely disabled and not started using by
false. By default it is enabled once it
is detected as a plugin.