http://www.couchbase.com/issues/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+NCBC+AND+resolution+%3D+Unresolved+AND+priority+%3D+Blocker+ORDER+BY+key+DESC An XML representation of a search request en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/NCBC-265 Couchbase .NET client library Blocker, because it's required before next release. NCBC-265

Refactor solution so that Enyim is part of main source branch

Improvement Blocker In Progress Unresolved John Zablocki John Zablocki Mon, 20 May 2013 08:54:23 -0500 Thu, 23 May 2013 12:07:53 -0500 1.2.6 1.2.7 0 1 Rank 11330 http://www.couchbase.com/issues/browse/NCBC-257 Couchbase .NET client library I&#39;m adding this bug to identify performance issue that is raised in CBSE-521 and CBSE-528 <br/> <br/> 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. <br/> These errors go away when the rebalance is over and with rebound phase, no errors are observed. <br/> Please see some sample reports: <br/> <a href="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_fo-ept-rb-Sdotnet-1.2-release-T2013-04-02-00.11.35-LV_MC_BASIC.txt</a> <br/> <a href="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_rb-2-in-Sdotnet-1.2-release-T2013-04-02-00.21.03-LV_HTTP_BASIC.txt</a> <br/> <a href="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">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</a> <br/> <br/> Mark - need your input here too, do you think these errors during rebalance can impact performance or stability at customer site. <br/> NCBC-257

During rebalance client tries to connect the primary node only

Bug Blocker Open Unresolved John Zablocki Saakshi Manocha Thu, 2 May 2013 08:20:59 -0500 Thu, 23 May 2013 06:51:16 -0500 1.2.6 1.2.7 library 0 4 Also, as per the documentation and our understanding, we can expect errors during CHANGE phase and ideally they should go away in REBOUND phase.<br/> <br/> CHANGE: Here we see that errors start happening. This is because a cluster topology change started around this time. We can expect errors until the topology change is completed. In this case, the topology change was adding a single node to the cluster.<br/> REBOUND: Here we see the errors are stopping. This is because the topology change has been completed. Since we added an extra node to the<br/> cluster, the rate of operations has actually gone up from before. This is because there are more nodes to handle requests now. This appears to be a critical issue. Marking as blocker for 1.2.7 until we have a better understanding. When you say &quot;connect to the primary node only&quot; are you referring to the streaming connection or all ops are going on the primary node? I ran the sdkd tests on a 4-node cluster. During the fail-over/rebalance phase, client automatically considers one node as the primary node and throughout the logs, the error is:<br/> &nbsp;System.IO.IOException: Failed to read from the socket &#39;10.3.3.206:11210&#39;. Error: SocketError value was Success, but 0 bytes were received<br/> <br/> It only tries to connect to the primary node, never tries to connect to the other nodes, and once the primary node is up and the rebalance is over, the error rate slows down. Rank 10975 http://www.couchbase.com/issues/browse/NCBC-78 Couchbase .NET client library Given the comments on this page: <a href="http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html">http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html</a> <br/> <br/> 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-78

Enhance discussion of return codes/values

Bug Blocker Open Unresolved John Zablocki Perry Krug Tue, 26 Jun 2012 09:31:05 -0500 Fri, 7 Dec 2012 21:41:33 -0600 1.1.6 1.3 docs 0 0 This is a must-have for SDK testing. It is very difficult to determine failure types and severities without knowing what types of errors, exception classes, or such to expect. <br/> <br/> At the very least, there should be standard return codes (in a well-defined location) for memcached error codes. Rank 9995