Skip to content

Latest commit

 

History

History
57 lines (50 loc) · 3.17 KB

engine-params.org

File metadata and controls

57 lines (50 loc) · 3.17 KB

EP Parameters

1 Configuring the Engine

Engine parameters may be specified using the -e option to memcached. These parameters control various aspects of the behavior of the engine.

For example, if you would like to store your database in /data/base and prevent it from having objects larger than 1MB, you would run memcached like this:

memcached -E ep.so -e 'dbfile=/data/base;max_item_size=1048576'

2 Parameters for the EP Engine

keytypedescr
config_filestringPath to additional parameters.
dbnamestringPath to on-disk storage.
ht_locksintNumber of locks per hash table.
ht_sizeintNumber of buckets per hash table.
initfilestringOptional SQL script to run after opening DB
postInitfilestringOptional SQL script to run after all DB
shards and statements have been initialized
max_item_sizeintMaximum number of bytes allowed for an item.
tap_backlog_limitintMax number of items allowed in a tap backfill
max_sizeintMax cumulative item size in bytes.
mem_high_watintAutomatically evict when exceeding this size.
mem_low_watintLow water mark to aim for when evicting.
min_data_ageintMinimum data stability time before persist.
queue_age_capintMaximum queue time before forcing persist.
tap_idstringLocal tap identifier for remote peer.
tap_idle_timeoutintTap client idle timeout.
tap_keepaliveintSeconds to hold open named tap connections.
tap_peerstringUpstream server to contact.
vb0boolIf true, start with an active vbucket 0
waitforwarmupboolWhether to block server start during warmup.
warmupboolWhether to load existing data at startup.
expiry_windowintexpiry window to not persist an object
that is expired (or will be soon)
exp_pager_stimeintSleep time for the pager that purges expired
objects from memory and disk
failpartialwarmupboolIf false, continue running after failing to
load some records.
db_shardsintNumber of shards for db store