The 2.7.3 release is a patch update, covering just one issue
which was intended to be in 2.7.2.
It's issue 181 (also SPY-60) and has to do with continuing
to search for another server in the list provided if one
server appears to be down.
Summary of changes since the 2.6 series:
(see previous 2.7 release notes for more details)
The 2.7 series gains significant new capabilities when using
binary protocol with Membase or forthcoming updates to
memcached.
Starting with the 2.7 release, it is now possible to
instantiate a MemcachedClient from the REST interface
supported by Membase. What this means is that if you have
one or more buckets in Membase, you can create
MemcachedClient objects to work with the buckets. Furthermore,
if the cluster topology changes (i.e. a node is added or
removed), the client will automatically adjust to the new
topology.
This updated client also has support for other new Membase
operations, some of which will likely be in memcached
as well in a future release:
touch - extend the expiration for a given item
get and touch (a.k.a. gat) - get and touch an item
getl - get and lock an item, with a lock expiration time
Bugs fixed/closed in 2.7.3:
http://code.google.com/p/spymemcached/issues/detail?id=181
(a.k.a. http://www.couchbase.org/issues/browse/SPY-60)
Bugs fixed/closed in 2.7.2:
http://code.google.com/p/spymemcached/issues/detail?id=125
http://code.google.com/p/spymemcached/issues/detail?id=166
http://code.google.com/p/spymemcached/issues/detail?id=190
http://code.google.com/p/spymemcached/issues/detail?id=193 (post release)
http://code.google.com/p/spymemcached/issues/detail?id=195
http://code.google.com/p/spymemcached/issues/detail?id=196
http://code.google.com/p/spymemcached/issues/detail?id=201
http://code.google.com/p/spymemcached/issues/detail?id=202
Bugs fixed/closed in 2.7.1:
http://code.google.com/p/spymemcached/issues/detail?id=96
http://code.google.com/p/spymemcached/issues/detail?id=134
http://code.google.com/p/spymemcached/issues/detail?id=152
http://code.google.com/p/spymemcached/issues/detail?id=171
http://code.google.com/p/spymemcached/issues/detail?id=187
Bugs fixed/closed in 2.7:
http://code.google.com/p/spymemcached/issues/detail?id=153
http://code.google.com/p/spymemcached/issues/detail?id=172
http://code.google.com/p/spymemcached/issues/detail?id=165
With others which can be listed here:
http://code.google.com/p/spymemcached/issues/list
Note that Couchbase also tracks issues here:
http://www.couchbase.org/issues/browse/SPY