Couchbase

[NCBC-258] Improvement needed around documentation of using singleton client

Fri, 24 May 2013 13:00:42 -0500

This has been coming up more and more lately. Apparently customers are not seeing or understanding the need for using a singleton client, even in their very basic testing.

Additionally, all of the tutorial and API examples in the documentation show the creation of a client for every operation and so tend to reinforce the bad habits.

Can we make an effort around identifying and improving the visibility of this very painful issue?

[NCBC-252] Docs/Library: Unlock after getl

Fri, 24 May 2013 12:58:56 -0500

Does the .NET client support an unlock? If not, will we have it? If it does, can we document it?

[NCBC-251] Certain method summaries are not linked properly in docs

Fri, 24 May 2013 12:57:53 -0500

I haven't checked all of them, but many links off of this page do not go anywhere: http://www.couchbase.com/docs/couchbase-sdk-net-1.2/api-reference-summary.html

For example, all the getwithlock links do not have documentation behind them.

[NCBC-260] Improve discussion around using store versus executestore

Fri, 24 May 2013 12:44:01 -0500

From a user:

Another thing I have seen is using set and exeuteset method usage. When in samples we are using set, it is not very clear that it might fail due to memory limitation and instead of using set we should use executeset and lookout for result and if it is fail due to memory issue than we should try again in few millisecond so couchbase do memory clean-up in mean time for new data.

[NCBC-222] When node is unavailable for a view query, don't throw an InvalidOperationException

Fri, 24 May 2013 12:42:48 -0500

When node is unavailable for a view query, don't throw an InvalidOperationException

[NCBC-248] Touch should return a boolean

Fri, 24 May 2013 12:37:55 -0500

If touch doesn't return anything then we need to at least update the documentation (with right now says touch returns a boolean) and explain how the user can know if the operation was successful.

[NCBC-162] Handle "no active vbucket" view failure

Fri, 24 May 2013 12:27:20 -0500

Presumably the client should try the view on another node..

In general we should have a unified exception class for view errors the client can understand.. InvalidOperationException is not very helpful or descriptive (nor is it very catchable.. though it was probably initially placed as a stub)..

[INFO 76.59 cbsdk.scenario failover.py:149] Ramp for 5 seconds..
[INFO 81.60 cbsdk.scenario failover.py:157] No service specified..
[ACTION 81.60 cbsdk.scenario failover.py:160] Failing over nodes [ip:10.3.121.207 ssh_username:root]
[ACTION 81.60 cbsdk.cluster.cluster cluster.py:695] Failing over node ip:10.3.121.207 ssh_username:root
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 143
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in \\vboxsrv\src\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run() in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.78 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Requested suppression of exception dialog box..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 143
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\HammockHttpClient.cs:line 112
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams) in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 144
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext() in \\vboxsrv\src\couchbase-net-client\src\Couchbase\CouchbaseViewHandler.cs:line 38
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run() in \\vboxsrv\src\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run() in \\vboxsrv\src\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Unhandled Exception System.InvalidOperationException Server returned Found: Moved Temporarily, {"error":"no_active_vbuckets","reason":"Cannot execute view query since the node has no active vbuckets"} at Couchbase.HammockHttpClient.HammockResponseWrapper.ExecuteWith(RestClient client)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.HammockHttpClient.HammockRequestWrapper.Couchbase.IHttpRequest.GetResponse()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at Sdkd.Views.ViewCommand.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.dispatchCommand(Request req)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at SdkdConsole.Daemon.Handle.Run()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] at System.Threading.ThreadHelper.ThreadStart()
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..
[SDKD(INFO) 81.79 cbsdk.sdkd.remote remote.py:263] [Sdkd.Main|Fatal] Will now exit..

[NCBC-174] Fix invalid tests in NUnit project.

Dependency — Fri, 24 May 2013 12:10:42 -0500

Fix invalid tests in NUnit project.

[NCBC-249] We need documentation that explains how users can check for error codes

Fri, 24 May 2013 12:09:56 -0500

I'm pretty sure that the .NET SDK allows us to do this, but I might be wrong. If we can properly check for errors we should document it.

[NCBC-152] Couchbase Client hangs during instantion of the Client if the request to http://xxx.xxx.xxx.xxx:8091/pools/default/bucketsStreaming/default is blocked or never returns

Fri, 24 May 2013 11:59:01 -0500

During instantiation of the client, a MessageStreamListener is created. Inside of the listener is a call is made to the config url

Line 376 of MessageStreamListener

this.request = this.requestFactory.GetWebRequest(configUrl, configUrl.GetHashCode().ToString());
this.response = this.request.GetResponse();

If this call never completes, for example because AVG silently blocks the request and prevents the data from being returned, then the client will wait indefinitely instead of timing out.

[NCBC-226] Docs: Reference installation

Thu, 23 May 2013 12:51:23 -0500

Customers have lots of choices at their fingertips, and many of those choices will result in a non-functioning installation, or at least a lot of time spent figuring out what the right pieces are.

Can we please provide as much details as possible about a reference installation that we can be sure will work for a customer who is just getting started? This is outside of our support for any one operatin system, but more about telling the customer "if you install with these versions and packages, this code will work"

-OS
-"language" version (.NET 4, etc)
-other packages/modules required and/or tested with

[NCBC-265] Refactor solution so that Enyim is part of main source branch

Thu, 23 May 2013 12:07:53 -0500

Refactor solution so that Enyim is part of main source branch

[NCBC-221] Docs: working with multiple buckets in the .NET client

Thu, 23 May 2013 11:19:09 -0500

Apologies if it's already in there, it wasn't particularly obvious to find.

Can we have a section of documentation on working with multiple buckets from within the .NET client when configured in the app.config?

[NCBC-84] Replica read command

Thu, 23 May 2013 11:02:44 -0500

Implement a simple replica read command

[NCBC-214] Docs don't mention InnerResult

Thu, 23 May 2013 11:02:08 -0500

The docs page on Working with Operation Results does not describe the InnerResult member at all. No mention of when it will be set, what it should contain, or how to display it.

My understanding is that this member may be important for understanding why something has failed. I'm not sure how to describe it or use it best, though, so I think this needs some clarification from SDK team.

[NCBC-223] Check for SetTcpKeepAlive at runtime for Mono support

Thu, 23 May 2013 09:53:21 -0500

Mono doesn't support this method on the ServicePointManager.

[NCBC-262] .Net client fails in two sdkd scenarios

Thu, 23 May 2013 06:51:59 -0500

.Net client is producing errors (socket reset, operation time out, etc) for two scenarios:

HYBRID_rb-1-swap (swap rebalance (one added, one removed))
HYBRID_svc-restart-75pct (restart couchbase-server on 3/4 nodes)

[NCBC-257] During rebalance client tries to connect the primary node only

Thu, 23 May 2013 06:51:16 -0500

I'm adding this bug to identify performance issue that is raised in CBSE-521 and CBSE-528

It is observed during the sdkd scenario tests, that while rebalance is happening, the client tries to connect only the primary node and does not connect to the other secondary nodes in the cluster. During rebalance the topology changes and hence many errors like socket reset, no response received, operation time out, etc.
These errors go away when the rebalance is over and with rebound phase, no errors are observed.
Please see some sample reports:
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_fo-ept-rb-Sdotnet-1.2-release-T2013-04-02-00.11.35-LV_MC_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_rb-2-in-Sdotnet-1.2-release-T2013-04-02-00.21.03-LV_HTTP_BASIC.txt
http://sdk-testresults.couchbase.com.s3.amazonaws.com/sdkd/HWIN-335SPEPOCGT-IHYBRID_fo-ept-eject-Sdotnet-1.2-release-T2013-04-02-00.17.30-LV_HTTP_BASIC.txt

Mark - need your input here too, do you think these errors during rebalance can impact performance or stability at customer site.

[NCBC-264] document the release process

Thu, 23 May 2013 05:45:34 -0500

Somewhere in the source repository, please document the release process.

[NCBC-266] Garbled error message when CAS value does not match

Tue, 21 May 2013 11:28:28 -0500

See the attached screenshot. This is reproducible whenever the client does a CAS operation with a CAS id that does not match. Code snippet attached as well.

[NCBC-111] Hangs after threads are aborted

Tue, 21 May 2013 03:10:35 -0500

In our production system thread occasionally get aborted to prevent long-running tasks from using resources when the user is no longer interested in the results. We are seeing these kinds of errors in the log:

ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl - Could not init pool.
and
ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl - Failed to reset an acquired socket.

Also, we are seeing hangs in MessageStreamListener.cs, line 400:
while ((line = reader.ReadLine()) != null)

This will occasionally hang indefinitely waiting for data to come in to the stream when there is no more data coming in.
I have created a reproduction application that creates a bunch of threads in an "abortable" thread pool (which just allows you to abort the threads, instead of being a black box). Starting the application will print a "." for every thread started, a "!" for every thread stopped and an "x" for every thread aborted. The thread itself just does a simple set/get. It typically hangs after about 15-20 seconds, on this ReadLine statement.

You can find the repro attached to this ticket.

This happens with Couchbase server 1.8.1 and the latest client code from Github.

[NCBC-204] JSON extension methods not listed in API references

Sat, 18 May 2013 05:29:31 -0500

Couldn't find docs around the JSON extension methods listed here:
https://www.couchbase.com/docs/couchbase-sdk-net-1.2/jsonextensions.html

[NCBC-188] Provide file based caching of config for stateless .NET apps

Fri, 17 May 2013 15:43:05 -0500

With stateless apps, such as WCF, it's not possible to create a static client variable that is used across the lifetime of the app. An alternate approach would be to write config to a file and update it periodically instead of bootstrapping with each object creation.

[NCBC-175] Authenticated view tests should use app.config

Fri, 17 May 2013 15:42:54 -0500

Authenticated view tests should use app.config

[NCBC-173] Use Couchbase.Management API to create buckets and views for unit tests requiring custom setups

Fri, 17 May 2013 15:42:43 -0500

Use Couchbase.Management API to create buckets and views for unit tests requiring custom setups

[NCBC-153] InvalidOperationException in views during server restart

Fri, 17 May 2013 15:42:27 -0500

'service couchbase-server restart' on the (only) node.

While it's easy to understand the reason for these errors, they should be wrapped a bit nicer. This is with doing GetItem() on each view request (and running them all inside a tight loop).

[Couchbase.MessageStreamListener|Warn] Current node 'http://10.0.0.99:8091/pools/default/bucketsStreaming/default?bucket
_uuid=e0a080ddc9d74fa3adbcbb9385f2ceae' has failed.
[Couchbase.MessageStreamListener|Warn] Could not found a working node.
[Couchbase.MessageStreamListener|Warn] All nodes are dead, sleeping for a while.
[Enyim.Caching.Memcached.MemcachedNode|Error] System.IO.IOException: Failed to read from the socket '10.0.0.99:11210'. E
rror: ConnectionReset
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couch
base-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\BasicNetworkStream.cs:line 92
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couchbase-net-client\lib
\EnyimMemcached\Enyim.Caching\Memcached\PooledSocket.cs:line 222
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket) in F:\couchbase-net-client\lib\En
yimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinaryResponse.cs:line 57
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket) in F:\couchbas
e-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinarySingleItemOperation.cs:line 24
   at Enyim.Caching.Memcached.Protocol.Operation.Enyim.Caching.Memcached.IOperation.ReadResponse(PooledSocket socket) in
F:\couchbase-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Operation.cs:line 27
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op) in F:\couchbase-net-client\lib\EnyimMemcache
d\Enyim.Caching\Memcached\MemcachedNode.cs:line 550
[Enyim.Caching.Memcached.MemcachedNode|Error] System.IO.IOException: Failed to read from the socket '10.0.0.99:11210'. E
rror: ConnectionReset
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couch
base-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\BasicNetworkStream.cs:line 92
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count) in F:\couchbase-net-client\lib
\EnyimMemcached\Enyim.Caching\Memcached\PooledSocket.cs:line 222
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket) in F:\couchbase-net-client\lib\En
yimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinaryResponse.cs:line 57
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket) in F:\couchbas
e-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Binary\BinarySingleItemOperation.cs:line 24
   at Enyim.Caching.Memcached.Protocol.Operation.Enyim.Caching.Memcached.IOperation.ReadResponse(PooledSocket socket) in
F:\couchbase-net-client\lib\EnyimMemcached\Enyim.Caching\Memcached\Protocol\Operation.cs:line 27
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op) in F:\couchbase-net-client\lib\EnyimMemcache
d\Enyim.Caching\Memcached\MemcachedNode.cs:line 550
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

Unhandled Exception:Unhandled Exception: [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dea
d node, failing.

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead
node, failing.

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() System.InvalidOperationException: Operation is not valid due to the cu
rrent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()System.InvalidOperationException: Operation is not valid due to the cur
rent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:
Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() [Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.
Unhandled Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:

[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped to a dead node, failing.

Unhandled Exception: System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()[Couchbase.CouchbaseView|Warn] View Couchbase.CouchbaseView was mapped
to a dead node, failing.

Unhandled Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()Unhandled Exception:[Couchbase.CouchbaseView|Warn] View Couchbase.Couch
baseView was mapped to a dead node, failing.

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Unhandled Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart() System.InvalidOperationException: Operation is not valid due to the cu
rrent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()System.InvalidOperationException: Operation is not valid due to the cur
rent state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Couchbase.CouchbaseViewBase`1.GetResponse() in F:\couchbase-net-client\src\Couchbase\CouchbaseViewBase.cs:line 209

   at Couchbase.CouchbaseViewBase`1.<TransformResults>d__0`1.MoveNext() in F:\couchbase-net-client\src\Couchbase\Couchba
seViewBase.cs:line 95
   at Sdkd.Views.ViewCommand.Run() in F:\sdkd-net\src\Sdkd\Views\ViewCommand.cs:line 219
   at SdkdConsole.Daemon.Handle.dispatchCommand(Request req) in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 177
   at SdkdConsole.Daemon.Handle.Run() in F:\sdkd-net\src\SdkdConsole\Daemon\Handle.cs:line 110
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, B
oolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

[NCBC-73] Need better explanation of usage and return values of increment operation (and likely others)

Fri, 17 May 2013 15:42:08 -0500

The current docs for incrememnt: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-update-increment.html

Can there be some attention paid to the above documentation (and will likely be needed across the board in similar areas):
-Some return values say: CasResult<ulong> (Cas result of bool). What is "Cas result of bool"?
-Other return values say: IMutateOperationResult (Mutate operation result). Is the same operation really expected to return drastically different object types?
-Some examples have "var casv = client.GetWithCas("inventory");" before performing the increment. Is it necessary to get the CAS id before performing this type of increment? Is it necessary to supply the CAS id for this type of increment?
-Some examples have very simply usage, others have more detail:
var getResult = client.ExecuteGet("inventory");

if (getResult.Success) {
var mutateResult client.ExecuteIncrement("inventory", 100, 1, getResult.Cas);

if (mutateResult.Success) {
logger.Debug("New value: " + mutateResult.Value);
}
}

-Can all of the examples be made consistent, and/or just have a single example at the top showing how to perform the incremement and work with the result. Then the various optional methods can be shown below?
-There seems to be a fair amount of duplication within the methods provided. For example, the last two are exactly the same (even have the same typo on "numvers") and there are other seemingly duplicates throughout.

[NCBC-68] Getting a thread abort (ocassionally) on store

Fri, 17 May 2013 15:41:26 -0500

http://www.couchbase.com/forums/thread/getting-thread-abort-ocassionally-store

Please follow up with this user on the forums after resolving this issue.

We are using the c# client to hit a couchbase 1.8 membase bucket. Every once in while (enough were it's bad) we are getting thread aborts during the store call. Here is the full stack of the error.

2012-06-11 02:59:39,819 [10] ERROR Knotice.Caching [(null)] <(null)> - Failed to add object to L2 cache with key: 297of type:SimpleDatabase msg:Thread was being aborted.
System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
   at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.PooledSocket.Read(Byte[] buffer, Int32 offset, Int32 count)
   at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket)
   at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket)
   at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op)
   at Couchbase.CouchbaseClient.ExecuteWithRedirect(IMemcachedNode startNode, ISingleItemOperation op)
   at Couchbase.CouchbaseClient.PerformStore(StoreMode mode, String key, Object value, UInt32 expires, UInt64& cas, Int32& statusCode)
   at Enyim.Caching.MemcachedClient.Store(StoreMode mode, String key, Object value, DateTime expiresAt)
   at Knotice.Caching.CacheManager.Store(Object key, Object item, Type type, Int32 tenantId, CacheSettings settings) in d:\Temp\Concentri\Dev - Full Build\Sources\Lib\Caching\Knotice.Caching\CacheManager.cs:line 109

[NCBC-29] programmatically set all the Couchbase configurations

Fri, 17 May 2013 15:40:53 -0500

We can programmatically set some the Couchbase configurations, however we cannot set the SocketPool settings Programmatically.

These settings can be set in the config file, but it would be nice to be able to set these through the program.

[NCBC-4] default logging on Enyim should include INFO level logging on connections being dropped

Fri, 17 May 2013 15:40:42 -0500

Per an email discussion, at least when using the COM wrapper, if not when using .NET calls directly, there may not be logging by default about connection drops/reconnects.

[NCBC-232] Fix CBSE-426 - .Net Client fails silently if there is a wrong configuration

Dependency — Fri, 17 May 2013 15:39:33 -0500

Fix CBSE-426 - .Net Client fails silently if there is a wrong configuration

[NCBC-207] Could not find the pool '...' at http://host:8091/pools : password-less buckets make the other buckets unavailable

Fri, 17 May 2013 15:39:11 -0500

Hi, we stumbled on a minor bug.

After importing the beer bucket for testing purpose, we had this kind of errors : (Couchbase .Net 1.2 / mono client)

2013-01-17 11:13:28 [DEBUG] 1 Couchbase.MessageStreamListener - Starting the listener. Queue=True
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Started working.
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Looking for the first working node.
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool 'static' at http://10.1.44.1:8091/pools
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url http://10.1.44.1:8091/pools; trying the next in the list
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool 'static' at http://10.1.44.2:8091/pools
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url http://10.1.44.2:8091/pools; trying the next in the list
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not found a working node.
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - All nodes are dead, sleeping for a while.
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Received new configuration.
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Config is empty, all nodes are down.
2013-01-17 11:13:29 [DEBUG] 11 Couchbase.MessageStreamListener - Processing message:

It appears that if a bucket with authentication is passwordless (like the beer sample bucket at creation), the client cannot find the other pools.

[NCBC-202] add a keyStats feature

Fri, 17 May 2013 15:38:20 -0500

At times it's useful to get information about a key through underlying "stats key <key> <vbucket>", but using just the stats command is complex because the vbucket hashing isn't exposed. One better though is a keyStats() operation that would return a map of the return for "stats key".

[NCBC-135] Client not properly handling cluster_run server

Fri, 17 May 2013 15:37:53 -0500

I can't do simple things like get/set stuff..

PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> .\cbc-net.exe -c set -k foo -V bar -H 10.0.0.99
:8091; .\cbc-net.exe -c get -k foo -H 10.0.0.99:8091
URI: http://10.0.0.99:8091/pools
http://10.0.0.99:8091/pools
Created new client..
Arguments to ExecuteStore:
0x00000003, 'foo', 'bar', 00:00:00, Zero, Zero
Operation Succeeded. Cas: 610018894666114
Duration was 3.07 Sec.
URI: http://10.0.0.99:8091/pools
http://10.0.0.99:8091/pools
Created new client..
Command OK
Value is bar
Cas is 610018894666114
Duration was 3.09 Sec.
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> echo "hi" | C:\Users\Administrator\Documents\Gi
tHub\deps\bin\cbc.exe create -h 10.0.0.99 foo2
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> # Now with the cluster_run cluster
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> .\cbc-net.exe -c set -k foo -V bar -H 10.0.0.99
:9000; .\cbc-net.exe -c get -k foo -H 10.0.0.99:9000
URI: http://10.0.0.99:9000/pools
http://10.0.0.99:9000/pools
Created new client..
Arguments to ExecuteStore:
0x00000003, 'foo', 'bar', 00:00:00, Zero, Zero
Initial command failed (Store operation failed, see InnerResult or StatusCode for details). Trying simple version..
.. Inner Message: Failed to execute operation
Command Failed
Code is 0
Message is Store operation failed, see InnerResult or StatusCode for details
Duration was 3.02 Sec.
URI: http://10.0.0.99:9000/pools
http://10.0.0.99:9000/pools
Created new client..
Command Failed
Code is
Message is Unable to locate node
Duration was 3.05 Sec.
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>

## This works fine with libcouchbase:

PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> echo "hi" | C:\Users\Administrator\Documents\Gi
tHub\deps\bin\cbc.exe create -h 10.0.0.99:9000 foo2
Stored "foo2" CAS:911342e1e62a0200
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug> C:\Users\Administrator\Documents\GitHub\deps\bi
n\cbc.exe cat -h 10.0.0.99:9000 foo2
"foo2" Size:3 Flags:0 CAS:911342e1e62a0200
hi
PS C:\Users\Administrator\Documents\GitHub\cbc-net\src\CbcNet\bin\Debug>

[NCBC-235] Provide more detail on "Unable to locate node" errors

Fri, 17 May 2013 15:37:27 -0500

Provide more detail on "Unable to locate node" errors

[NCBC-242] ExecuteGet-multi should return detailed status results for each key

Fri, 17 May 2013 15:36:54 -0500

ExecuteGet-multi should return detailed status results for each key

[NCBC-170] evaluate socket pool reliability change

Fri, 17 May 2013 15:35:29 -0500

A recent issue seems to be similar to a reported issue in EnyimMemcached. We should evaluate whether or not to include this in our release.

See https://github.com/enyim/EnyimMemcached/issues/94

[NCBC-219] Write the .NET/Windows Getting Started Section for the Essentials Guides

Fri, 17 May 2013 15:34:18 -0500

Write the .NET/Windows Getting Started section of the Essentials Guide

Needs to cover:

Basic Setup of the .NET environment
Adding the .NET Client library to a project
Writing your first (small) app using Couchbase and .NET

Submissions should be to MC, either through the couchbase/docs repo, or direct to MC in whatever format suits. Must include both the text and images.

[NCBC-215] BinaryOperation failues should include message

Fri, 17 May 2013 15:32:52 -0500

When the client is unable to process the response from the server, there should be some notification, probably via BinaryOperationResult.Message

[NCBC-196] Config updates seem to be occuring when vbucket configuration hasn't changed

Fri, 17 May 2013 15:30:54 -0500

The client appears to be updating its config when receiving config updates that shouldn't trigger a change in internal config (i.e., reodered nodes, fast forward maps).

[NCBC-198] When performing MultiGet, unloading AppDomain crashes the host

Fri, 17 May 2013 15:30:21 -0500

https://github.com/enyim/EnyimMemcached/issues/103

[NCBC-183] Docs should use Execute* methods with best practice error handling and logging in all examples

Fri, 17 May 2013 15:21:39 -0500

While proper error handling may be application-specific (some apps may be fine treating any error as "not found", while others need to handle those as very distinct cases, for example), I think the documentation the docs provide, and especially the tutorials and examples that people are likely to copy from, should perform explicit and thorough error handling and logging. Docs should make it easy for people to do it the right way.

The current .NET docs have an OK example in the ASP.NET tutorial, where at least the return value is checked and exceptions are rethrown. So that's a good start, although there's no evidence of testing result.Success (which could be false, even if result.Exception is null). There's no mention, too, of what happens higher up when the result code is returned, and no logging of errors that folks can cut and paste.

http://www.couchbase.com/docs/couchbase-sdk-net-1.2/brewerycrud.html

One method uses this:
return result.StatusCode.HasValue ? result.StatusCode.Value : 0;

While the others just return result.StatusCode.Value with no test. Why is that? Where is that documented?

Then this example uses the non-Execute versions which don't allow for proper error handling. That may be OK in a very basic tutorial, but there should be a very clear and explicit pointer anywhere these are used that goes to a "Error handling with the .NET client" page that details why you shouldn't use those in most production code, and that you'll have a very hard time writing correct code unless you use the Execute* methods, and that also provides succinct and complete example for cut-and-pastability of correct error handling.

Even so, I'd prefer that the basic "hello world" tutorial use Execute* methods in the first place, so people who only skim the docs only see the correct way to do things.

http://www.couchbase.com/docs/couchbase-sdk-net-1.2/crud.html

[NCBC-253] flush_all method still available through API, does nothing against 2.0 cluster

Tue, 14 May 2013 15:43:51 -0500

Is flush_all deprecated for 2.x clusters? No error is returned when run against a 2.0 bucket

Need SDK documentation on the deprecation and how to use flush properly (it's currently only in the release notes)

[NCBC-261] Use an enumeration instead of integers for return codes

Tue, 14 May 2013 10:11:08 -0500

Customer suggested an improvement of using an enumeration for the operation results instead of integer values.

[NCBC-233] Enhance packaging to not conflict with other tools that include Enyim.Caching via Nuget

Duplicate — Wed, 8 May 2013 13:56:47 -0500

The CouchbaseClient nuget package includes Enyim.Caching which causes compatibility issues with 3rd party applications also relying on the Enyim.Caching assembly.

The third party tool we were looking at using was ServiceStack's Caching interface, specifically the Memcached client implementation. This tool was where were were getting the conflict as they include the Enyim.Caching assembly as a nuget dependency.

See also http://www.couchbase.com/issues/browse/CBSE-412

[NCBC-225] Docs: Recommendations for which logging level to be set during testing/staging/production and examples of messages at each level

Wed, 8 May 2013 13:56:00 -0500

Customer read http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-logging.html, but still not clear on what level we recommend to get meaningful output from, and examples of what log messages that would see under certain situations.

[NCBC-244] Explicit docs for what .NET Framework versions are supported

Mon, 6 May 2013 13:55:42 -0500

Need to be explicit about what versions of Visual Studio are supported, and what .NET Framework is supported. 3.5? 4.0?

The docs mention that you need the full .NET Framework, not just a Client profile. But don't mention if 4.0 is needed. It seems that 3.5 is not supported, but I'm not positive.

[NCBC-250] Fix the test : CouchbaseAuthenticatedViewTests\When_Bucket_Is_Authenticated_View_Returns_Results

Tue, 9 Apr 2013 05:46:57 -0500

Fix the following test in .Net library, it is constantly failing:

Test Class: CouchbaseAuthenticatedViewTests
Test Name: When_Bucket_Is_Authenticated_View_Returns_Results

Reason for failure:
There is no document/view getting created in SASL bucket with name "authenticated".
Instead the code creates the documents/views in "default" bucket since the code uses the default initialization of couchbase client which uses the "default" bucket.

[NCBC-179] Add expiries and CAS to StoreJson extension methods

Wed, 20 Feb 2013 09:39:50 -0600

Add expiries and CAS to StoreJson extension methods

[NCBC-58] Way to determine which Servers are active

Mon, 18 Feb 2013 10:24:52 -0600

Can there a way to determine if there are no available Couchbase servers?
There should be someway to check the status of the cluster from the Client.

[NCBC-12] logging level documentation needed

Thu, 7 Feb 2013 06:18:48 -0600

Currently, there's insufficient information on how to change the logging level to see what's happening when diagnosing an issue.

[NCBC-77] Need details on "StoreMode" values

Wed, 6 Feb 2013 06:06:27 -0600

In this page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html

There is no detail on what the available store modes are (set/add/replace)

[NCBC-220] Error handling documentation

Tue, 5 Feb 2013 02:39:17 -0600

Please create some documentation specifying possible error/failures to operations, what they "look" like in the logs/exceptions/stack traces and what our recommendation is on how to handle them.

i.e. tmp_oom, timeouts (connection/operation/java-internal/etc), "get miss" (it's technically a failure, let's make it overly obvious what it means), CAS failure, add() failure, replace() failure,

Some of this should be covered in the API reference, but this bug is specifically for a single page where this information is aggregated that a customer/user could read about how to handle errors.

[NCBC-78] Enhance discussion of return codes/values

Fri, 7 Dec 2012 21:41:33 -0600

Given the comments on this page: http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html

Perhaps there can be a section on the possible return codes/values, what they mean, when they might happen, and how to deal with them?

[NCBC-126] Implement keep-alive logic for data connections

Wed, 28 Nov 2012 04:10:53 -0600

A customer has been experiencing connection resets due to a firewall in place between the application servers and Couchbase closing idle connections.

While we have a heartbeat on 8091, we do not for 11210.

This is necessary to prevent the firewall from seeing these connections as idle.

[NCBC-123] Set, add, and replace should be separate methods

Tue, 23 Oct 2012 17:15:24 -0500

Set, add, and replace should be separate methods

[NCBC-113] CouchbaseCluster RESTful wrappers should not expose WebExceptions

Mon, 8 Oct 2012 10:43:25 -0500

CouchbaseCluster RESTful wrappers should not expose WebExceptions

[NCBC-41] As a .net developer, I have an API that allows me to access all of the features of tap so that I can make use of all of the powers of membase.

Mon, 8 Oct 2012 10:42:51 -0500

As a .net developer, I have an API that allows me to access all of the features of tap so that I can make use of all of the powers of membase.

[NCBC-39] Minimize key size by storing as binary array

Fri, 5 Oct 2012 13:38:02 -0500

To reduce overall memory consumption, and make most efficient use of resources, the client should be able to store data as a binary array instead of in a string representation. For example, a GUID which might take 36 bytes as a string can be stored as a 20-byte binary array.

However, the .NET client API doesn't provide any means to store non-string representations of keys, so we're not able to maximize efficiency in this way.

[NCBC-13] generating shippable artifacts

Fri, 5 Oct 2012 13:37:44 -0500

generating shippable artifacts

[NCBC-14] building under CI

Fri, 5 Oct 2012 13:37:34 -0500

building under CI

[NCBC-17] building shippable artifacts under CI

Fri, 5 Oct 2012 13:37:13 -0500

building shippable artifacts under CI

[NCBC-16] running integration tests under CI

Fri, 5 Oct 2012 13:37:03 -0500

running integration tests under CI

[NCBC-18] deploying to download locations directly from CI

Fri, 5 Oct 2012 13:36:53 -0500

The idea here is that interim builds, as they come through code review, generate artifacts and upload to a given location. If they're actual release builds, they upload to a different location. This could also go to nuget, if appropriate.

[NCBC-36] Enhance intelligence of client to know about all nodes of a cluster for making REST connection

Fri, 5 Oct 2012 13:33:59 -0500

If configured with a single host (a load balancer), the client will pause for 1s everytime it loses this connection. The same thing happens when configured with a list of hosts and the client reaches the end of the list...it pauses for 1s before going back to the top.

I don't think it's appropriate to ask for the client to constantly spin on trying to make a connection if in fact none can be made.

Another solution to this would be to have the client be aware of ALL the servers in a cluster (which it gets via the vbucket map info) and be able to try all of them, and/or know which ones are alive so that it doesn't have to wait

[NCBC-44] Optimize multiple set (multi-set or mset bulk update) with setq

Fri, 5 Oct 2012 13:31:46 -0500

The Java client, and others, implement a more efficient bulk loading feature when multiple updates are sent to the cluster at one time. They use setq to send multiple requests without needing to round-trip the result after each one.

The .NET client does not implement this; it only implements a multi-get operation. The multi-set is important for efficiently loading data.

This probaby doesn't have to be Couchbase-specific, but would apply to vanilla memcached servers, too.

[NCBC-81] ExecuteGet() for DictionaryType on multiple keys does not throw a exception if it is not able to connect to a node

Fri, 5 Oct 2012 13:25:15 -0500

For development purposes i'm using a local Couchbase server installation with a single node. So i guess that turning off the CouchbaseServer service means the whole cluster in my case.
Here's a simple demo code:

System.Configuration.Configuration cfg = ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.None);
ICouchbaseClientConfiguration section = cfg.GetSection("Couchbase") as ICouchbaseClientConfiguration;

using (CouchbaseClient client = new CouchbaseClient(section))
{
IOperationResult res = client.ExecuteStore(Enyim.Caching.Memcached.StoreMode.Set, "Test1", 1);
Console.WriteLine("Set1 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);

res = client.ExecuteStore(Enyim.Caching.Memcached.StoreMode.Set, "Test2", 2);
Console.WriteLine("Set2 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);

IDictionary<string, IGetOperationResult> multigetRes = client.ExecuteGet(new string[] { "Test1", "Test2" });
Console.WriteLine("Dictionary count: {0}", multigetRes.Count);

foreach (KeyValuePair<string, IGetOperationResult> kvp in multigetRes)
{
Console.WriteLine("Get {0} Success:{1}, StatusCode: {2} Message: {3}", kvp.Key, kvp.Value.Success, kvp.Value.StatusCode, kvp.Value.Message);
}
}

Output with CouchbaseServer service on:
Set1 Success:True StatusCode:0 Message:
Set2 Success:True StatusCode:0 Message:
Dictionary count: 2
Get Test1 Success:True, StatusCode: Message:
Get Test2 Success:True, StatusCode: Message:

Output with CouchbaseServer service off:
Set1 Success:False StatusCode: Message:Failed to locate node
Set2 Success:False StatusCode: Message:Failed to locate node
Dictionary count: 0

Singular gets result in the correct exception error message:
Modified demo:
System.Configuration.Configuration cfg = ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.None);
ICouchbaseClientConfiguration section = cfg.GetSection("Couchbase") as ICouchbaseClientConfiguration;
using (CouchbaseClient client = new CouchbaseClient(section))
{
IOperationResult res = client.ExecuteStore(Enyim.Caching.Memcached.StoreMode.Set, "Test1", 1);
Console.WriteLine("Set1 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);
res = client.ExecuteStore(Enyim.Caching.Memcached.StoreMode.Set, "Test2", 2);
Console.WriteLine("Set2 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);
IDictionary<string, IGetOperationResult> multigetRes = client.ExecuteGet(new string[] { "Test1", "Test2" });
Console.WriteLine("Dictionary count: {0}", multigetRes.Count);
foreach (KeyValuePair<string, IGetOperationResult> kvp in multigetRes)
{
Console.WriteLine("MultiGet {0} Success:{1}, StatusCode: {2} Message: {3}", kvp.Key, kvp.Value.Success, kvp.Value.StatusCode, kvp.Value.Message);
}
res = client.ExecuteGet("Test1");
Console.WriteLine("Get1 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);
res = client.ExecuteGet("Test2");
Console.WriteLine("Get2 Success:{0} StatusCode:{1} Message:{2}", res.Success, res.StatusCode, res.Message);
}

Output:
Set1 Success:False StatusCode: Message:Failed to locate node
Set2 Success:False StatusCode: Message:Failed to locate node
Dictionary count: 0
Get1 Success:False StatusCode: Message:Unable to locate node
Get2 Success:False StatusCode: Message:Unable to locate node

[NCBC-97] Stats call doesn't handle I/O error

Fri, 5 Oct 2012 13:24:18 -0500

Repeat as follows:

- Call to MemcachedClient.Stats(type)
- This builds a StatsOperation for each node and asynchronously performs MemcachedNode.Execute(cmd)
- An I/O error occurs, so StatsOperation leaves its member "results" as null and Execute returns false to indicate an error
- MemcachedClient ignores the returned Boolean value from EndInvoke and puts a null dictionary into its own set of results
- ServerStats.GetRaw(key) dies trying to select into the missing dictionary

Plausible fix: check the status from EndInvoke and don't stick anything in the dictionary if there was an error.

[NCBC-100] Provide Extract of Comments for API Docs

Fri, 5 Oct 2012 13:23:35 -0500

Need to be able to generate extract of comments, preferrably including method signatures for .NET

[NCBC-99] Provide Error Handling Consistent with Other SDKs

Fri, 5 Oct 2012 13:23:10 -0500

Provide Error Handling Consistent with Other SDKs and underlying protocol.

[NCBC-101] Provide Consistent Timeouts

Fri, 5 Oct 2012 13:22:44 -0500

Provides the consistent level of time outs with other SDKs. Provide ability to set timeouts at: 1) connection, 2) authentication, and 3) ops level.

[NCBC-102] Provide Standardized Logging

Fri, 5 Oct 2012 13:22:14 -0500

Provides the consistent level of logging provided by other SDKs. Provide more information on configuring logging for developers.

[NCBC-103] Provide Consistent Order of Parameters

Fri, 5 Oct 2012 13:21:43 -0500

Provide consistent, predictable order for method parameters as other SDKS.

[NCBC-120] Statistics through Stats() Enyim.Caching.MemcachedClient.

Fri, 5 Oct 2012 13:15:41 -0500

User is collecting statistics and would like to collect some of the histogram type data that is available for specific stats through cbstats timings.

Particularly: "disk_insert" and "item_alloc_sizes" with the Stats command to get data as described in 2.5 Timing Stats for link: https://github.com/membase/ep-engine/blob/master/docs/stats.org.

They would like to be able to do this through Enyim.Caching.dll as it is already used by their "Core" code so they support statistics gathering with what that interface offers and like its simplicity.

Currently the dll support memcached specific stats but not ep-engine.

Enhancment request is to expand the functionality of the stats call in Enyim.Caching