A few memcachedb questions

[Chris Bunch]

Hi there,
We're looking to use memcachedb and while setting it up, I had a
few questions.

1) The documentation mentions a number of functions in the patched
memcache.py that I can't find in it. I have the newest non-beta
version of memcache (1.2.0) and while it does have two of the new
functions, 'rep_set_ack_policy', 'rep_set_priority', it doesn't have
the others mentioned, such as whoismaster or ismaster. Where can I get
these other functions?

2) Is the beta version (1.2.1-beta) stable enough to use? It's been
beta for a while now but I had chosen the non-beta precisely because I
wanted a stable version of memcachedb to use.

3) When using the patched memcache.py, should I specify all the
machines running memcachedb or just the master?

-- If I specify just the master, how does whoismaster work when the
master fails?

-- If I specify all the nodes, how does the library know who to write
to since there's only one master and I'm not specifying who it is?

Thanks much for your time! Memcachedb so far has been extremely simple
to set up and we would love to get it up and going on our systems;
thanks for putting it out there!

[Steve Chu]

On Fri, Nov 6, 2009 at 2:37 AM, Chris Bunch <shattere...@gmail.com> wrote:
>
> Hi there,
>   We're looking to use memcachedb and while setting it up, I had a
> few questions.
>
> 1) The documentation mentions a number of functions in the patched
> memcache.py that I can't find in it. I have the newest non-beta
> version of memcache (1.2.0) and while it does have two of the new
> functions, 'rep_set_ack_policy', 'rep_set_priority', it doesn't have
> the others mentioned, such as whoismaster or ismaster. Where can I get
> these other functions?
>

They are discarded, use 'stats rep', 'stats repms' instead. same 'def
get_stats(self, subcmd=''):' in memcache.py.

> 2) Is the beta version (1.2.1-beta) stable enough to use? It's been
> beta for a while now but I had chosen the non-beta precisely because I
> wanted a stable version of memcachedb to use.
>

Actually, the trunk code is stable enough...we deploy a lot. But not
much changes since 1.2.1-beta.

> 3) When using the patched memcache.py, should I specify all the
> machines running memcachedb or just the master?
>
> -- If I specify just the master, how does whoismaster work when the
> master fails?
>
> -- If I specify all the nodes, how does the library know who to write
> to since there's only one master and I'm not specifying who it is?
>

memcache.py does not do this for you, you should maintain the group
membership by yourself. If mastership changes, change your dns hook,
or some other naming system.

> Thanks much for your time! Memcachedb so far has been extremely simple
> to set up and we would love to get it up and going on our systems;
> thanks for putting it out there!
>
> >
>

--
Best Regards,

Steve Chu
http://stvchu.org

[Steve Chu]

Besides, if you want to use replication of memcachedb, patch
bdb-4.7.25 first(there's bug in bulk transfer), patches are here:
http://www.oracle.com/technology/products/berkeley-db/db/update/4.7.25/patch.4.7.25.html

On Fri, Nov 6, 2009 at 2:37 AM, Chris Bunch <shattere...@gmail.com> wrote:
>