Skip to content

membase shard compatible mutilate - #3

Open
Repter75 wants to merge 6 commits into
leverich:masterfrom
Repter75:master
Open

membase shard compatible mutilate#3
Repter75 wants to merge 6 commits into
leverich:masterfrom
Repter75:master

Conversation

@Repter75

Copy link
Copy Markdown

No description provided.

syang0 added 6 commits March 8, 2013 05:38
This version ONLY supports one server, has no agent mode, and takes
in a vbucket configuration through a file.

Since this does not yet include the auto-configuration updater thread
and thus works without locking the vBucket map, it should be the fastest
possible implementation.

A config.txt file is included that maps all vBuckets to zephyr5. To run,

./mutilate --server=zephyr5-10G:11210 -T 8 --binary --username=default
	--membaseConfig=config.txt

Note: omitting the last parameter will result in a test without using
vBuckets, which is equivalent to the previous commit of mutilate.
preparation for supporting multiple connections to different
servers in a single "Connection" object.

All the response states for GET and SET have been condensed into
one state that solely checks for the # of CLRFs. It trades off
value length checking for modularity.
…rnal

socket connection (bufferevent) for membase/pisces.

In this world, a single membase/pisces Connection is equivalent to having 1
connection to every server node in the cluster.
…tion

don't wait for each other to connect before changing read_state to IDLE.
…code

for membaseConfigs. Both should aid with merge back with mainstream mutilate.
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

Successfully merging this pull request may close these issues.

2 participants