History log of /2.1.1/moxi/ (Results 1 - 25 of 1992)
Revision (<<< Hide revision tags) (Show revision tags >>>)Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
Revision tags: v5.0.0, v4.6.0, v4.5.0, v4.0.0, v3.1.0, v3.0.2, v3.0.1, v3.0.0, 2.5.0, 2.1.1r
af05d11c14-Jun-2013 Trond Norbye <trond.norbye@gmail.com>

Require libconflate

We are using libconflate in our product so it shouldn't be
optional. This simplifies the move towards CMake

Change-Id: Icb49849018d8c0a60436c62a5a87114edf470

Require libconflate

We are using libconflate in our product so it shouldn't be
optional. This simplifies the move towards CMake

Change-Id: Icb49849018d8c0a60436c62a5a87114edf470eaf
Reviewed-on: http://review.couchbase.org/26953
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Trond Norbye <trond.norbye@gmail.com>

show more ...

b938c31c14-Jun-2013 Trond Norbye <trond.norbye@gmail.com>

Require libmemcached

We are currently building moxi with libmemcached in our
product, and this commit is part of the process to simplify
our build process. By removing everything we

Require libmemcached

We are currently building moxi with libmemcached in our
product, and this commit is part of the process to simplify
our build process. By removing everything we don't use it'll
be easier to know which parts needs moving over to CMake.

Change-Id: I9f2073636099ba59bb645b6b867973a78289e958
Reviewed-on: http://review.couchbase.org/26952
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Trond Norbye <trond.norbye@gmail.com>

show more ...

057308b614-Jun-2013 Trond Norbye <trond.norbye@gmail.com>

Require libvbucket

We are currently building moxi with libvbucket in our
product, and this commit is part of the process to simplify
our build process. By removing everything we don'

Require libvbucket

We are currently building moxi with libvbucket in our
product, and this commit is part of the process to simplify
our build process. By removing everything we don't use it'll
be easier to know which parts needs moving over to CMake.

Change-Id: I7258260405f95a281f4fd37b3c98fa4488b0daac
Reviewed-on: http://review.couchbase.org/26951
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Trond Norbye <trond.norbye@gmail.com>

show more ...

Revision tags: 2.0.1-linux
4b39102116-Jan-2013 Trond Norbye <trond.norbye@gmail.com>

CBD-774: Add support for automake 1.13

Change-Id: Ib53a7885b31e6840545aea274f590d671d55d469
Reviewed-on: http://review.couchbase.org/23975
Reviewed-by: Michael Wiederhold <mike@couch

CBD-774: Add support for automake 1.13

Change-Id: Ib53a7885b31e6840545aea274f590d671d55d469
Reviewed-on: http://review.couchbase.org/23975
Reviewed-by: Michael Wiederhold <mike@couchbase.com>
Tested-by: Michael Wiederhold <mike@couchbase.com>

show more ...

Revision tags: 1.8.1
52a5fa8808-Jun-2012 Steve Yen <steve.yen@gmail.com>

MB-5488: SERVER_ERROR flush_all not supported

Change-Id: Ia080f82c03a23b3ee059471d37f63174e279be7d
Reviewed-on: http://review.couchbase.org/16989
Reviewed-by: Farshid Ghods <farshid@

MB-5488: SERVER_ERROR flush_all not supported

Change-Id: Ia080f82c03a23b3ee059471d37f63174e279be7d
Reviewed-on: http://review.couchbase.org/16989
Reviewed-by: Farshid Ghods <farshid@couchbase.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

1caa47df07-Jun-2012 Farshid Ghods <farshid.ghods@gmail.com>

MB-5305 use PRODUCT_VERSION instead of git_describe if it is set

Change-Id: Iffe38ee2df32255c2f9d6389d781ed1032badd55
Reviewed-on: http://review.couchbase.org/16957
Reviewed-by: Stev

MB-5305 use PRODUCT_VERSION instead of git_describe if it is set

Change-Id: Iffe38ee2df32255c2f9d6389d781ed1032badd55
Reviewed-on: http://review.couchbase.org/16957
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Farshid Ghods <farshid@couchbase.com>
Reviewed-by: Farshid Ghods <farshid@couchbase.com>

show more ...

ab77923f06-Jun-2012 Aliaksej Artamonau <aliaksiej.artamonau@gmail.com>

MB-5462 Use MKDIR_P instead of mkdir_p in install-data-hook.

mkdir_p has been deprecated since automake 1.12.1 and will be removed
in 1.13. And it seems that some brave GNU/Linux distrib

MB-5462 Use MKDIR_P instead of mkdir_p in install-data-hook.

mkdir_p has been deprecated since automake 1.12.1 and will be removed
in 1.13. And it seems that some brave GNU/Linux distributions already
decided to remove it.

Change-Id: I9e615a05dab16d10a8de922548220e1b5f541fed
Reviewed-on: http://review.couchbase.org/16868
Tested-by: Aliaksey Artamonau <aliaksiej.artamonau@gmail.com>
Reviewed-by: Steve Yen <steve.yen@gmail.com>

show more ...

cb602b1f26-Apr-2012 Steve Yen <steve.yen@gmail.com>

MB-4334 - clear downstream timeout before releasing

There's one code path in cproxy_release_downstream() where a
cproxy_forward() fails, during a retry, possibly while the downstream

MB-4334 - clear downstream timeout before releasing

There's one code path in cproxy_release_downstream() where a
cproxy_forward() fails, during a retry, possibly while the downstream
timeout_tv event is still regsitered. In that case, a downstream
could be released that has a non-0 timeout_tv. It's a small window
that some users have hit.

Change-Id: I1b87298dba1151c8ece51c0cd78d68ca6fa2bdb0
Reviewed-on: http://review.couchbase.org/15232
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

08dc908d30-Mar-2012 Steve Yen <steve.yen@gmail.com>

CBSE-126 - clear links & timeouts before and after releasing conn

THe new zstored / asynchronous connect()'ing feature introduced
code that didn't cleanup correctly in two places.

CBSE-126 - clear links & timeouts before and after releasing conn

THe new zstored / asynchronous connect()'ing feature introduced
code that didn't cleanup correctly in two places.

First, when a downstream was released (cproxy_release_downstream()),
the downstream should be de-linked before looping through
downstream_conns and repeatedly invoking
zstored_release_downstream_conn(). The reason is that
zstored_release_downstream_conn() calls cproxy_forward(), which might
recurse.

Secondly, when a downstream conn is zstored_release()'ed, the next
chosen waiting downstream needs to have its timeout cleared.
Otherwise, the (incorrectly) still-registered timeout "might" fire in
unexpected places, possibly leading to bug CBSE-126 situation,
although it's not a proven linkage.

Change-Id: Ib3fb8365a606a9a8260ac59a4e2d1dba00851d24
Reviewed-on: http://review.couchbase.org/14423
Reviewed-by: Bin Cui <bin.cui@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

5f01fa8a20-Mar-2012 Steve Yen <steve.yen@gmail.com>

Added config.cache to .gitignore

Change-Id: Ic4b4377ece415b675b9563e1af10ac0e12aa076c
Reviewed-on: http://review.couchbase.org/14130
Reviewed-by: Aliaksey Kandratsenka <alkondratenko

Added config.cache to .gitignore

Change-Id: Ic4b4377ece415b675b9563e1af10ac0e12aa076c
Reviewed-on: http://review.couchbase.org/14130
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

0ba14da720-Mar-2012 Steve Yen <steve.yen@gmail.com>

CBSE-115 - bug in the very first multiget command

The 1.8.0 feature to enable event-based, asynchronous downstream
connect()'ing (instead of the old synchronous downstream
connect()'

CBSE-115 - bug in the very first multiget command

The 1.8.0 feature to enable event-based, asynchronous downstream
connect()'ing (instead of the old synchronous downstream
connect()'ing) apparently introduced a bug with multi-get.

When the first request is a multi-get command that actually has
multiple key parameters, that first request can sometimes fail,
because an asynchronously connect()'ing downstream conn is left
registered in libevent. So, libevent might sometimes inadvertently
invoke the on_pause() callbacks which closes the downstream conns.

An existing unit tests for STATS (which also uses a broadcast codepath
like multiget) seems to sometimes catch this.

./t/issue-MB-3076.sh

After this fix of unregistering the half connected downstream conn
from libevent, test for MB-3076 passes.

Change-Id: Ia197a033fc7fece39055cf4bf3ea23c1e576ebc6
Reviewed-on: http://review.couchbase.org/14129
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

e50dd80115-Mar-2012 Steve Yen <steve.yen@gmail.com>

MB-4896 - Fix memory leak during dynamic reconfiguration.

The downstream data structs in moxi didn't have their
behavior data structures cleaned up.

Change-Id: Id96740f47f508b19

MB-4896 - Fix memory leak during dynamic reconfiguration.

The downstream data structs in moxi didn't have their
behavior data structures cleaned up.

Change-Id: Id96740f47f508b194e45990a1b580cbbfaabbefd
Reviewed-on: http://review.couchbase.org/13939
Reviewed-by: Bin Cui <bin.cui@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>

show more ...

Revision tags: 1.8.0
3119473a19-Nov-2011 Steve Yen <steve.yen@gmail.com>

X out passwords from stats proxy

The "stats proxy" command will now show XXX'ed out passwords,
like...

STAT 11211:test:info:config { "name": "test", "saslPassword": "XXXXXXXX"

X out passwords from stats proxy

The "stats proxy" command will now show XXX'ed out passwords,
like...

STAT 11211:test:info:config { "name": "test", "saslPassword": "XXXXXXXX"

Change-Id: I0edc0f0b9c017abdbdba47b75e88f4ba4802243d
Reviewed-on: http://review.couchbase.org/11037
Tested-by: Steve Yen <steve.yen@gmail.com>
Reviewed-by: Bin Cui <bin.cui@gmail.com>

show more ...

Revision tags: 1.7.2
6a04074713-Sep-2011 Steve Yen <steve.yen@gmail.com>

Capture the dtrace scripts from Dustin Sallings

Change-Id: I6ecd29edb4d310edebda717b5793ff0ea0ae11ea
Reviewed-on: http://review.couchbase.org/9563
Tested-by: Steve Yen <steve.yen@gma

Capture the dtrace scripts from Dustin Sallings

Change-Id: I6ecd29edb4d310edebda717b5793ff0ea0ae11ea
Reviewed-on: http://review.couchbase.org/9563
Tested-by: Steve Yen <steve.yen@gmail.com>
Reviewed-by: Steve Yen <steve.yen@gmail.com>

show more ...

0f3a435f10-Oct-2011 Steve Yen <steve.yen@gmail.com>

cproxy_forward assert(d->upstream_conn != NULL) cproxy.c, 1925

Here's the (rather involved) scenario where the assert would be triggered...

* start a rebalance. The rebalance shoul

cproxy_forward assert(d->upstream_conn != NULL) cproxy.c, 1925

Here's the (rather involved) scenario where the assert would be triggered...

* start a rebalance. The rebalance should be slow, where each vbucket
migration takes awhile.

* a multi-get command (with lots of keys) is processed by moxi, and
moxi scatters out downstream GET requests to the involved nodes.

* one downstream request will result in a NOT_MY_VBUCKET response from
a node, which will make moxi register for a retry of the command
again later (XXX).

* a different downstream request hits a pending vbucket, meaning it's
going to block moxi on that request, so moxi can't make progress on
that multi-get command.

* the rebalance is going very slowly, so next...

* moxi's downstream_timeout timer gets fired, so...

* moxi sends an error back up to the upstream client.

* THEN, since a retry was registered at step XXX above due to the
NOT_MY_VBUCKET, moxi next incorrectly goes through retry codepaths
and the assert() catches this bad move.

Change-Id: I4aea4e130ad55bbd2400bbbcd0547a86bddbc5da
Reviewed-on: http://review.couchbase.org/10039
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

1853268724-Sep-2011 nimish gupta <nigupta@zynga.com>

Unit test script for enabling event on downstream connection

Change-Id: Id6329c5bb9cebed6d1231a8aff00dfd465e19e5a
Reviewed-on: http://review.couchbase.org/9744
Reviewed-by: Steve Yen

Unit test script for enabling event on downstream connection

Change-Id: Id6329c5bb9cebed6d1231a8aff00dfd465e19e5a
Reviewed-on: http://review.couchbase.org/9744
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

a17b424822-Sep-2011 nimish gupta <nigupta@zynga.com>

Moxi change for enabling event on downstream connection in pause state

when we put the downstream connection in conn_pause state, we disable the
events on that. So if the connection get

Moxi change for enabling event on downstream connection in pause state

when we put the downstream connection in conn_pause state, we disable the
events on that. So if the connection get closed, we know only when we linked
that connection to upstream connection ,forward the upstream command to that
connection and wait for read event on that.When we wait for read event,
we come to know that connection has closed.
This fix is to enable read event on the downstream connection in pause state,
so we will know if server send extra data for a command or closes the connection.

Change-Id: Iff50b252a04a8036bb901849953eac557ef8cf9d
Reviewed-on: http://review.couchbase.org/9717
Tested-by: Steve Yen <steve.yen@gmail.com>
Reviewed-by: Steve Yen <steve.yen@gmail.com>

show more ...

d5076d9c21-Sep-2011 nimish gupta <nigupta@zynga.com>

Adding changes for binary protocol when key with getl is not found

This is related to change ID Ib1114094064e1bb7cc9ae42e412f3ab3a934fe0c.
Extending the same fix for binary protocol.

Adding changes for binary protocol when key with getl is not found

This is related to change ID Ib1114094064e1bb7cc9ae42e412f3ab3a934fe0c.
Extending the same fix for binary protocol.

Change-Id: Ibee2df61a726b70330104353097b528730b874fa
Reviewed-on: http://review.couchbase.org/9690
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

a6fae63a13-Sep-2011 nimish gupta <nigupta@zynga.com>

Moxi in compatibility mode crashed after downstream timeout

when there is not free downstream connection, downstream is put into the downstream
queue, and if the downstream conn queue ti

Moxi in compatibility mode crashed after downstream timeout

when there is not free downstream connection, downstream is put into the downstream
queue, and if the downstream conn queue timeout happens, we try to remove it from the
downstream queue but it is not removed from the queue since the host identifier is different
during insert and remove in the downstream queue and if the downstream connection is
closed, we try to send error to all downstream waiting.Then we try to send error to
released downstream which don't have upstream and moxi crashed.

Change-Id: I789618a617878e04bd65449cad5dff9f78a256c2
Reviewed-on: http://review.couchbase.org/9547
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

c0e094a513-Sep-2011 nimish gupta <nigupta@zynga.com>

Moxi in mcmux mode give error if default(or behaviour) downstream protocol is ascii

when moxi running in mcmux mode, if client want to use binary protocol between
moxi and membase, it wi

Moxi in mcmux mode give error if default(or behaviour) downstream protocol is ascii

when moxi running in mcmux mode, if client want to use binary protocol between
moxi and membase, it will send B:host:port <command>, so the peer_protocol of
upstream connection will be binary but we will send still in ascii to membase since
default behaviour is ascii. When we get response from membase, we check that that
upstream connection's peer protocol is binary, so try to parse ascii response with
binary handler and it fails.

Change-Id: I26f097bc7d20a0e11c76560c8be54a9dda6b05b1
Reviewed-on: http://review.couchbase.org/9554
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

120c83da13-Sep-2011 nimish gupta <nigupta@zynga.com>

Moxi returns END when key with getl is not found

ep-engine returns NOT_FOUND when getl is done with non-existent key but moxi converts
the NOT_FOUND to END and send END to client

Moxi returns END when key with getl is not found

ep-engine returns NOT_FOUND when getl is done with non-existent key but moxi converts
the NOT_FOUND to END and send END to client

Change-Id: Ib1114094064e1bb7cc9ae42e412f3ab3a934fe0c
Reviewed-on: http://review.couchbase.org/9551
Reviewed-by: Steve Yen <steve.yen@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

1fb2447716-Aug-2011 Trond Norbye <trond.norbye@gmail.com>

Include <sys/types.h> early in config_static.h

Not all platforms provide a tcp.h that can be included without
the types defined there...

Change-Id: I7a44b9a035e220addbc9c0e2eb54

Include <sys/types.h> early in config_static.h

Not all platforms provide a tcp.h that can be included without
the types defined there...

Change-Id: I7a44b9a035e220addbc9c0e2eb54acbee8ae3c6b
Reviewed-on: http://review.couchbase.org/9007
Tested-by: Trond Norbye <trond.norbye@gmail.com>
Reviewed-by: Chiyoung Seo <chiyoung.seo@gmail.com>

show more ...

5ee6012212-Aug-2011 Trond Norbye <trond.norbye@gmail.com>

Build strsep for platforms who don't have one

Change-Id: I5526e52d1ad0f183c65394447fe3e6881a2ff03d
Reviewed-on: http://review.couchbase.org/8906
Reviewed-by: Srinivas Vadlamani <srin

Build strsep for platforms who don't have one

Change-Id: I5526e52d1ad0f183c65394447fe3e6881a2ff03d
Reviewed-on: http://review.couchbase.org/8906
Reviewed-by: Srinivas Vadlamani <srinivas@couchbase.com>
Tested-by: Srinivas Vadlamani <srinivas@couchbase.com>

show more ...

Revision tags: 1.7.1
6a26e91a06-Jul-2011 Steve Yen <steve.yen@gmail.com>

MB-2897 - use 64-bits for msec_current time

32-bits overlows after 49+ days, and 64-bits should be enough for
anybody.

Change-Id: I769839ee4cb41f10ce808cf7f669c0cd1beb7245
R

MB-2897 - use 64-bits for msec_current time

32-bits overlows after 49+ days, and 64-bits should be enough for
anybody.

Change-Id: I769839ee4cb41f10ce808cf7f669c0cd1beb7245
Reviewed-on: http://review.couchbase.org/7748
Reviewed-by: Bin Cui <bin.cui@gmail.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

d85361d223-Jun-2011 Steve Yen <steve.yen@gmail.com>

MB-4003 - Allow empty binary stats values, part 2

Change-Id: Ice66eff1997d9c98d2542c02735d892bf9d2b696
Reviewed-on: http://review.couchbase.org/7151
Reviewed-by: Bin Cui <bin.cui@gma

MB-4003 - Allow empty binary stats values, part 2

Change-Id: Ice66eff1997d9c98d2542c02735d892bf9d2b696
Reviewed-on: http://review.couchbase.org/7151
Reviewed-by: Bin Cui <bin.cui@gmail.com>
Reviewed-by: Michael Wiederhold <mike@couchbase.com>
Tested-by: Steve Yen <steve.yen@gmail.com>

show more ...

12345678910>>...80