Searched +hist:0 +hist:c44517d (Results 1 - 11 of 11) sorted by path
/3.0.3-GA/ep-engine/src/ | ||
H A D | atomic.h | diff ebbcca4c Tue Dec 17 10:11:01 UTC 2013 Trond Norbye <trond.norbye@gmail.com> Cast the 0 in assignment to the type Change-Id: I201bea9d39d9b93dbce2c57f08ba91c2ce6e5679 Reviewed-on: http://review.couchbase.org/31195 Reviewed-by: Trond Norbye <trond.norbye@gmail.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> diff 40446cd0 Thu May 20 07:20:17 UTC 2010 Dustin Sallings <dustin@spy.net> RCValue copy constructor should start with a 0 refcount. Change-Id: I9aed4743645848bb027fa2a6b179f2dc0e00e547 Reviewed-on: http://review.northscale.com:8080/126 Tested-by: Dustin Sallings <dustin@spy.net> Reviewed-by: Sean Lynch <seanl@literati.org> |
H A D | ep_engine.cc | diff 0db302e5 Wed Aug 06 18:34:59 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11299: Don't let replica vbuckets send partial snapshots Replica vbuckets cannot create their own snapshots and must rely on the snapshots it received from the active vbucket when forwarding the snapshots to a downstream consumer. In order to make sure that this happens properly we will only stream mutations from the closed checkpoint for non-active vbuckets. This will guarantee that the above requirement is met. Change-Id: I58151ce96868e34083f87dca0ce1d18b6a12aedf Reviewed-on: http://review.couchbase.org/40346 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff a81b2dfd Wed Jul 09 18:39:05 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10962 Don't snooze the connection notifier unnecessarily. There is a race in pausing and resuming the connection notifier upon receiving a new mutation. To address this issue, This change adds a flag that indicates if there is a pending notification event for any TAP connections. Note that this change was originally merged in 2.5.0 branch to address the sporadic high latency issue in TAP-based replication. We still need to address it in the UPR-based replication separately. Change-Id: Ia8d39220c46647a21254c63f37e7ce3ceaa2bc99 Reviewed-on: http://review.couchbase.org/39250 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 0e2e2ab9 Tue Jun 24 19:28:44 UTC 2014 Sriram Ganesan <sriram@couchbase.com> MB-11362: Add dcp and dcpagg stats Add dcp and dcp agg stats that effectively point to upr and upragg stats respectively. upr and upragg will be deprecated once all the clients of those stats move to dcp Change-Id: Id77301e62c23215ff97f6ee06eba82f5f64b4652 Reviewed-on: http://review.couchbase.org/38854 Reviewed-by: David Liao <david.liao@couchbase.com> Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Sriram Ganesan <sriram@couchbase.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 4a5d415e Mon Jun 23 11:32:18 UTC 2014 Trond Norbye <trond.norbye@gmail.com> Release cluster configuration during shutdown > ::findleaks -v BYTES LEAKED VMEM_SEG CALLER 12288 6 fffffd7ffc35f000 MMAP 12288 1 fffffd7ffcf6c000 MMAP 12288 1 fffffd7ffcd6d000 MMAP 12288 1 fffffd7ffc95c000 MMAP 12288 1 fffffd7ffc75d000 MMAP 12288 1 fffffd7ffc55e000 MMAP ------------------------------------------------------------------------ Total 6 oversized leaks, 73728 bytes CACHE LEAKED BUFCTL CALLER 0000000000485028 1 00000000089d0380 ep.so`MemoryTracker::MemoryTracker+0x6b 00000000004a5028 1 0000000009b92ee0 ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f 000000000048a028 512 00000000098300e0 libstdc++.so.6.0.17`operator new+0x1e ------------------------------------------------------------------------ Total 514 buffers, 40968 bytes > 0000000009b92ee0::bufctl -v ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS 9b92ee0 df8f000 c39fa1a13ad83 4 4a5028 0 0 libumem.so.1`umem_cache_alloc_debug+0xfd libumem.so.1`umem_cache_alloc+0xb3 libumem.so.1`umem_alloc+0x64 libumem.so.1`malloc+0x3f ep.so`EventuallyPersistentEngine::setClusterConfig+0x5f ep.so`processUnknownCommand+0x73a ep.so`EvpUnknownCommand+0x38 bucket_engine.so`bucket_unknown_command+0x23d default_unknown_command+0xb8 process_bin_unknown_packet+0xa9 process_bin_packet+0xc6 complete_nread+0x182 conn_nread+0x48 event_handler+0x1ce libevent_core-2.0.so.5.1.9`event_base_loop+0x436 Change-Id: I093d7d7112701e7c23bb9522246489d532668aa6 Reviewed-on: http://review.couchbase.org/38659 Reviewed-by: Dave Rigby <daver@couchbase.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> |
H A D | ep_engine.h | diff 0e2e2ab9 Tue Jun 24 19:28:44 UTC 2014 Sriram Ganesan <sriram@couchbase.com> MB-11362: Add dcp and dcpagg stats Add dcp and dcp agg stats that effectively point to upr and upragg stats respectively. upr and upragg will be deprecated once all the clients of those stats move to dcp Change-Id: Id77301e62c23215ff97f6ee06eba82f5f64b4652 Reviewed-on: http://review.couchbase.org/38854 Reviewed-by: David Liao <david.liao@couchbase.com> Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Sriram Ganesan <sriram@couchbase.com> diff 46201d31 Sat Mar 01 01:32:20 UTC 2014 abhinavdangeti <abhinav@couchbase.com> MB-10117: Implementation of CMD_GET_KEYS api Request: - opcode: CMD_GET_KEYS: 0xb8 - extlen: 4B - ext: | COUNT(4B) | *if extlen = 0, then count defaults on 1000 Response - Body: |key1len(2B) |key1 |key2len(2B) |key2 |.... - Bodylen: Total length of the buffer, sent in the body Change-Id: I885f93e90114b62f63fa43822caac56cce15ac2a Reviewed-on: http://review.couchbase.org/33417 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 46201d31 Sat Mar 01 01:32:20 UTC 2014 abhinavdangeti <abhinav@couchbase.com> MB-10117: Implementation of CMD_GET_KEYS api Request: - opcode: CMD_GET_KEYS: 0xb8 - extlen: 4B - ext: | COUNT(4B) | *if extlen = 0, then count defaults on 1000 Response - Body: |key1len(2B) |key1 |key2len(2B) |key2 |.... - Bodylen: Total length of the buffer, sent in the body Change-Id: I885f93e90114b62f63fa43822caac56cce15ac2a Reviewed-on: http://review.couchbase.org/33417 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff ca67f157 Tue Jan 14 01:55:04 UTC 2014 abhinavdangeti <abhinav@couchbase.com> MB-8552: Support for datatype field - As part of extended flexible metadata - Requires: http://review.couchbase.org/#/c/30974/ In memory:: __________________________________________________ | key | MetaData (cas,exp,flags) | VALUE BLOB | |_____|_____________________________|______________| VALUE BLOB: __________________________________________________ | FLEX_META_CODE (1B) | DATATYPE (1B) | VALUE BLOB | |_____________________|_______________|____________| FLEX_META_CODE = 0x01, indicating one field in the extended metadata section In couchstore:: METADATA BUFFER: _______________________________________________________________________ | cas (8B) | exp (4B) | flags (4B) | FLEX_META_CODE (1B) | datatype(1B) | |__________|__________|____________|_____________________|______________| Change-Id: Ifb3bc59892130f2fddf02f2188773ba3a67f2ce1 Reviewed-on: http://review.couchbase.org/31046 Reviewed-by: Trond Norbye <trond.norbye@gmail.com> Tested-by: Trond Norbye <trond.norbye@gmail.com> diff 79a9d87d Thu Dec 19 19:29:22 UTC 2013 David Liao <liaodw@gmail.com> MB-9638 UPR persistence sequence number command This command is similar to the Tap checkpoint persistence command. But we use sequence number instead of checkpoint id for UPR. Refactored code to support both checkpoint id and seqno persistence. The new memcached command opcode is CMD_SEQNO_PERSISTENCE 0xb7. Added a stat "persistence_seqno". Added a test case "upr_persistence_seqno". Change-Id: Iec5db260e05cfa8889f253c33bb08209eb87ca2c Reviewed-on: http://review.couchbase.org/30899 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff de6d1bf1 Wed Oct 30 21:57:56 UTC 2013 abhinavdangeti <abhinav@couchbase.com> MB-8727: Cluster Configuration Carrier Publication Addresses MB-8727: - CMD_SET_CLUSTER_CONFIG: 0xb4 Addresses MB-8728: - CMD_GET_CLUSTER_CONFIG: 0xb5 - Cluster config Blob will be saved as it is received and will be returned as it is, with assumption that blob will be of JSON type, and that SDK will need to check the type of the document to differentiate between older and new version of couchbase. Addresses MB-8729: - NOT_MY_VBUCKET to return cluster config blob instead of the "not my vbucket" message. - Memcached change: http://review.couchbase.org/#/c/29844/ For memcached to retrieve Cluster Configuration from ep_engine in case of ENGINE_NOT_MY_VBUCKET response. - bucket_engine change: http://review.couchbase.org/#/c/29845/ Change-Id: I20cf4aa145139d19524f252d3444dd0f52d0965d Reviewed-on: http://review.couchbase.org/29684 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff de6d1bf1 Wed Oct 30 21:57:56 UTC 2013 abhinavdangeti <abhinav@couchbase.com> MB-8727: Cluster Configuration Carrier Publication Addresses MB-8727: - CMD_SET_CLUSTER_CONFIG: 0xb4 Addresses MB-8728: - CMD_GET_CLUSTER_CONFIG: 0xb5 - Cluster config Blob will be saved as it is received and will be returned as it is, with assumption that blob will be of JSON type, and that SDK will need to check the type of the document to differentiate between older and new version of couchbase. Addresses MB-8729: - NOT_MY_VBUCKET to return cluster config blob instead of the "not my vbucket" message. - Memcached change: http://review.couchbase.org/#/c/29844/ For memcached to retrieve Cluster Configuration from ep_engine in case of ENGINE_NOT_MY_VBUCKET response. - bucket_engine change: http://review.couchbase.org/#/c/29845/ Change-Id: I20cf4aa145139d19524f252d3444dd0f52d0965d Reviewed-on: http://review.couchbase.org/29684 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> |
H A D | vbucket.cc | diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 1ba4011d Sat Jan 18 02:22:17 UTC 2014 Sundar Sridharan <sundar.sridharan@gmail.com> MB-9919: Provide DB data size and file size stats This change provides DB data size and file size per vbucket and their aggregated values through stats call. stats "vbucket-details vbucket_id" returns the list of a given vbucket's stats including its DB data size and file size. For example, "vbucket-details 0" includes the following stats for vbucket 0: 1) vb_0:db_data_size --> DB data size for vbucket 0 2) vb_0:db_file_size --> DB file size for vbucket 0 On the other hand, stats "all" includes the aggregated DB data size and file size: 1) ep_db_data_size --> DB data size aggreaged across all vbuckets. 2) ep_db_file_size --> DB file size aggregated across all vbuckets. A test case is added to ensure the value ticks up correctly. Change-Id: Id8ae17ae7726f9a003a3245defc2ccf4ee89b77c Reviewed-on: http://review.couchbase.org/32533 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff 79a9d87d Thu Dec 19 19:29:22 UTC 2013 David Liao <liaodw@gmail.com> MB-9638 UPR persistence sequence number command This command is similar to the Tap checkpoint persistence command. But we use sequence number instead of checkpoint id for UPR. Refactored code to support both checkpoint id and seqno persistence. The new memcached command opcode is CMD_SEQNO_PERSISTENCE 0xb7. Added a stat "persistence_seqno". Added a test case "upr_persistence_seqno". Change-Id: Iec5db260e05cfa8889f253c33bb08209eb87ca2c Reviewed-on: http://review.couchbase.org/30899 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff c82b067b Thu Jun 27 20:13:46 UTC 2013 Jin Lim <jin@couchbase.com> MB-8679 Add pendingVbs queue to bgfetcher This queue allows bgfetcher to visit only those vbuckets in the given shard that have pending bgfetch requests. This optmizes scheduling bgfetch requests in more efficient fifo way. Rebalance should benefit the above enhancement most, and initial test shows below performance increase. <Reb-1-out-3-buckets> 2.1.0-718-rel || 2.1.1-with-this-fix Time hrs 4.48 || 3.83 Rebalance Time (sec) 3095 || 2578 Sets (90-95-99) (ms) 11 – 17 – 53 || 6 – 9 – 18 Gets (90-95-99) (ms) 13 – 20 – 208 || 9 – 14 – 164 Ops (avg) 2.40k || 1.48k Change-Id: Iadbbcb069701da947aac2a8cbc0d8b30762a13a4 Reviewed-on: http://review.couchbase.org/27178 Reviewed-by: Chiyoung Seo <chiyoung.seo@gmail.com> Tested-by: Chiyoung Seo <chiyoung.seo@gmail.com> diff 0d6b7b00 Mon May 13 22:49:00 UTC 2013 Jin Lim <jin@couchbase.com> MB-8231 flusher must continue checkpoint persistence for empty vbucket This fixes the current doHighPriority logic that incorrectly assumes there must be always pending mutation (low priority vbucket persistence) when more than one vbucket is marked for checkpoint persistence. Otherwise, this could cause the rebalance to hang when ns server issues the checkpoint_persistence cmd over empty vbucket or vbuckets being created. Change-Id: I4d23d1d49c8f6e9c23041afbf65137312e77ce2f Reviewed-on: http://review.couchbase.org/26275 Tested-by: Jin Lim <jin@couchbase.com> Reviewed-by: Jin Lim <jin@couchbase.com> diff 977b7e94 Wed Jun 27 20:37:13 UTC 2012 Chiyoung Seo <chiyoung.seo@gmail.com> MB-5711 New active vbucket starts with the open checkpoint id > 1 Consider the following scenario: 1. Node A started and has the active vb 0 with the open checkpoint 1 2 Load some items into the open checkpoint 1 3. Restart A and then A will still have the open checkpoint 1 after warmup, which is now empty. 4. Node B is newly joined and has the empty replica vb0 starting with the open checkpoint 1 5. Replication from A to B for vb0 doesn't schedule backfill because we thought that both node A and B have the synchronized open checkpoint for vb0. Change-Id: Iea90be1db41ef060f03619247ab61e1f3faddfdc Reviewed-on: http://review.couchbase.org/17688 Reviewed-by: Jin Lim <jin@couchbase.com> Tested-by: Chiyoung Seo <chiyoung.seo@gmail.com> diff d79f65ca Mon Jul 11 20:42:01 UTC 2011 Chiyoung Seo <chiyoung.seo@gmail.com> MB-4034 Set open checkpoint Id to 1 if vbucket's state sets to active If the state of a given vbucket with open checkpoint Id 0 sets to active, its open checkpoint Id should set to 1 as the active vbucket should always start with checkpoint Id 1. Change-Id: I8b075b91c525162cea6d0fa5f52521d91e1910cc Reviewed-on: http://review.couchbase.org/7879 Reviewed-by: Srinivas Vadlamani <srinivas@couchbase.com> Tested-by: Chiyoung Seo <chiyoung.seo@gmail.com> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
/3.0.3-GA/ep-engine/src/atomic/ | ||
H A D | gcc_atomics.h | 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
H A D | libatomic.h | diff 0f23c3fe Mon Oct 11 12:43:02 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Fixed 32 bit builds on Solaris Change-Id: Ie5fb70e9e1b59fb7c4fc1309657e06ce3ba02f5e Reviewed-on: http://review.membase.org/3223 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
/3.0.3-GA/ep-engine/tests/ | ||
H A D | ep_testsuite.cc | diff a3f61753 Thu Feb 19 23:10:31 UTC 2015 Manu Dhundi <manu@couchbase.com> MB-13479: Indicate rollback to DCP clients if purge_seqno > snap_start_seqno The replica may not get all the items if there are purged items in the active node. Hence this solution proposes to indicate a rollback to seqno 0 in case the purge_seqno > snap_start_seqno. Note: Since the occurrence of this scenario is pretty rare, rolling back to 0 may not be a bad thing. Change-Id: I5c8403115110be136df5d4cb4e2704edc2a4c9e4 Reviewed-on: http://review.couchbase.org/47094 Tested-by: Manu Dhundi <manu@couchbase.com> Reviewed-by: Michael Wiederhold <mike@couchbase.com> diff a3f61753 Thu Feb 19 23:10:31 UTC 2015 Manu Dhundi <manu@couchbase.com> MB-13479: Indicate rollback to DCP clients if purge_seqno > snap_start_seqno The replica may not get all the items if there are purged items in the active node. Hence this solution proposes to indicate a rollback to seqno 0 in case the purge_seqno > snap_start_seqno. Note: Since the occurrence of this scenario is pretty rare, rolling back to 0 may not be a bad thing. Change-Id: I5c8403115110be136df5d4cb4e2704edc2a4c9e4 Reviewed-on: http://review.couchbase.org/47094 Tested-by: Manu Dhundi <manu@couchbase.com> Reviewed-by: Michael Wiederhold <mike@couchbase.com> diff 0db302e5 Wed Aug 06 18:34:59 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11299: Don't let replica vbuckets send partial snapshots Replica vbuckets cannot create their own snapshots and must rely on the snapshots it received from the active vbucket when forwarding the snapshots to a downstream consumer. In order to make sure that this happens properly we will only stream mutations from the closed checkpoint for non-active vbuckets. This will guarantee that the above requirement is met. Change-Id: I58151ce96868e34083f87dca0ce1d18b6a12aedf Reviewed-on: http://review.couchbase.org/40346 Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff 0c903de4 Wed May 28 18:23:41 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11592: Create snapshots when getting items from the chk queues This change introduces a new flag to indicate whether or not ep-engine should create a new checkpoint for this snapshot. This flag is used internally by ep-engine and only ep-engine. We are also changing the flags values for snapshot markers since they weren't really flags previously. Below are the new values. Disk 0x01 Memory 0x02 Checkpoint 0x04 Change-Id: I8a262eb7856c97e11e95570fbdaef82f3f79054a Reviewed-on: http://review.couchbase.org/38779 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff 0c903de4 Wed May 28 18:23:41 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11592: Create snapshots when getting items from the chk queues This change introduces a new flag to indicate whether or not ep-engine should create a new checkpoint for this snapshot. This flag is used internally by ep-engine and only ep-engine. We are also changing the flags values for snapshot markers since they weren't really flags previously. Below are the new values. Disk 0x01 Memory 0x02 Checkpoint 0x04 Change-Id: I8a262eb7856c97e11e95570fbdaef82f3f79054a Reviewed-on: http://review.couchbase.org/38779 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff 0c903de4 Wed May 28 18:23:41 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11592: Create snapshots when getting items from the chk queues This change introduces a new flag to indicate whether or not ep-engine should create a new checkpoint for this snapshot. This flag is used internally by ep-engine and only ep-engine. We are also changing the flags values for snapshot markers since they weren't really flags previously. Below are the new values. Disk 0x01 Memory 0x02 Checkpoint 0x04 Change-Id: I8a262eb7856c97e11e95570fbdaef82f3f79054a Reviewed-on: http://review.couchbase.org/38779 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff 0c903de4 Wed May 28 18:23:41 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-11592: Create snapshots when getting items from the chk queues This change introduces a new flag to indicate whether or not ep-engine should create a new checkpoint for this snapshot. This flag is used internally by ep-engine and only ep-engine. We are also changing the flags values for snapshot markers since they weren't really flags previously. Below are the new values. Disk 0x01 Memory 0x02 Checkpoint 0x04 Change-Id: I8a262eb7856c97e11e95570fbdaef82f3f79054a Reviewed-on: http://review.couchbase.org/38779 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff 0e2e2ab9 Tue Jun 24 19:28:44 UTC 2014 Sriram Ganesan <sriram@couchbase.com> MB-11362: Add dcp and dcpagg stats Add dcp and dcp agg stats that effectively point to upr and upragg stats respectively. upr and upragg will be deprecated once all the clients of those stats move to dcp Change-Id: Id77301e62c23215ff97f6ee06eba82f5f64b4652 Reviewed-on: http://review.couchbase.org/38854 Reviewed-by: David Liao <david.liao@couchbase.com> Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Sriram Ganesan <sriram@couchbase.com> diff f991533e Tue May 13 04:39:01 UTC 2014 Mike Wiederhold <mike@couchbase.com> MB-10640 Improve UPR rollback during failover. Stream request now has snap_start_seqno and snap_end_seqno. (high_seqno is removed) which can be used to deal with partial snapshot. failover check is based on start_seqno, snap_start_seqno and snap_end_seqno. Snapshot Marker now has start_seqno, end_seqno and flag. start_seqno/end_seqno indicates sequence number ranges of the stream. The flag indicates if a stream is from disk or memory. The current value are: 0: memory 1: disk Change-Id: I4f7528f453e1f0c3021ab51f2173e111ed4a17e9 Reviewed-on: http://review.couchbase.org/35198 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Tested-by: Michael Wiederhold <mike@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> diff b770547a Tue Mar 25 20:01:33 UTC 2014 Chiyoung Seo <chiyoung.seo@gmail.com> MB-10406 Unlock a locked item on replica vbucket for replication GetAndLock causes the replication or rebalance operation to fail in the following scenario: 1) Rebalance starts and is in progress 2) Active vbucket 0 is moving from Node 1 to Node 2 3) Item A on active vbucket 0 on Node 1 is locked through getLocked() API while vbucket 0 is still being transferring. 4) Active vbucket 0 is transferred to Node 2. Node 1 changes vbucket 0 state to replica. 5) Item A on active vbucket 0 on Node 2 is updated through Set() API. 6) Node 2 tries to replicate the updated Item A to the node 1, but receives an error code (ENGINE_KEY_EEXISTS) from Node 1 because Item A is still locked due to the step 3). 7) Node 2 closes the TAP connection to Node 1 because of the above error code, which is a bug in the engine side. To resolve the above issue, we should unlock a locked item on replica vbucket. Change-Id: I5200b9f8f1864ed8ff5388dc7a621c205c589047 Reviewed-on: http://review.couchbase.org/34902 Reviewed-by: Michael Wiederhold <mike@couchbase.com> Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com> Tested-by: Chiyoung Seo <chiyoung@couchbase.com> |
H A D | ep_testsuite.h | 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
/3.0.3-GA/ep-engine/tests/mock/ | ||
H A D | mock_dcp.h | 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
/3.0.3-GA/ep-engine/tests/module_tests/ | ||
H A D | threadtests.h | diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
H A D | vbucket_test.cc | diff 56c80678 Tue May 15 14:42:54 UTC 2012 Sergey Avseyev <sergey.avseyev@gmail.com> Include unistd.h for usleep(3) Fixes compiler errors like this: In file included from vbucket.hh:18:0, from backfill.cc:3: stored-value.hh: In destructor 'HashTable::~HashTable()': stored-value.hh:973:23: error: 'usleep' was not declared in this scope Change-Id: I7bc2c26a8e7e1fec928d51f36a78ba028a6486d7 Reviewed-on: http://review.couchbase.org/16024 Tested-by: Sergey Avseyev <sergey.avseyev@gmail.com> Reviewed-by: Trond Norbye <trond.norbye@gmail.com> Reviewed-by: Chiyoung Seo <chiyoung.seo@gmail.com> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> diff 0c44517d Fri Oct 01 21:16:54 UTC 2010 Trond Norbye <trond.norbye@gmail.com> Compile fixes for Sun Studio compilers Change-Id: I087fbe83c239ec7934d57400f714d8c3906dd04a Reviewed-on: http://review.northscale.com/2942 Reviewed-by: Dustin Sallings <dustin@spy.net> Tested-by: Dustin Sallings <dustin@spy.net> |
Completed in 418 milliseconds