[MB-12448] [windows] online upgrade from 2.5.1 to 3.0.1-1444 failed Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Test Blocker
Reporter: Thuan Nguyen Assignee: Thuan Nguyen
Resolution: Unresolved Votes: 0
Labels: windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: windows 2008 R2 64-bit

Attachments: Zip Archive 12.11.10.145-10242014-1844-diag.zip     Zip Archive 12.11.10.146-10242014-1845-diag.zip    
Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Install couchbase server 2.5.1 on one windows 2008 R2 64-bit (node 145)
Create default bucket.
Install couchbase server 3.0.1-1444 on another windows 2008 R2 64-bit (node 146)
Add 3.0.1 node (146) to 2.5.1 node (145).
Rebalance. Rebalance hang at 0% a while then failed with error:

Rebalance exited with reason {not_all_nodes_are_ready_yet,
['ns_1@12.11.10.146']}
ns_orchestrator002 ns_1@12.11.10.146 18:42:50 - Fri Oct 24, 2014
Port server memcached on node 'babysitter_of_ns_1@127.0.0.1' exited with status 255. Restarting. Messages: ns_log000 ns_1@12.11.10.146 18:42:38 - Fri Oct 24, 2014

Then see memcached crashed continuously on 3.0.1 node with exit 255


 Comments   
Comment by Aleksey Kondratenko [ 24/Oct/14 ]
it is totally unrelated to upgrade. 3.0.1 node simply fails to boot memcached.
Comment by Aleksey Kondratenko [ 24/Oct/14 ]
I'm not able to rdp to .146 as well. So cannot diagnose further.

It does look like either totally broken package for 3.0.1 on windows or some very bad environment issue.
Comment by Thuan Nguyen [ 24/Oct/14 ]
It's is my local box. I will reproduce in our server.




[MB-12447] Check the memory condition before allocating Item instance in ItemAllocate API Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 2.5.1
Fix Version/s: 3.0.1, 3.0.2
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Chiyoung Seo Assignee: Chiyoung Seo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Link to Log File, atop/blg, CBCollectInfo, Core dump: http://www.couchbase.com/issues/browse/CBSE-1426
http://www.couchbase.com/issues/browse/CBSE-1279
Is this a Regression?: Unknown

 Comments   
Comment by Matt Ingenthron [ 24/Oct/14 ]
I don't think it's possible to ship this on 2.5.1, which shipped long ago. Probably need a different fix version here.
Comment by Matt Ingenthron [ 24/Oct/14 ]
Possibly related to MB-12420?




[MB-12446] queries against views have changed from 2.x to 3.x Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Matt Ingenthron Assignee: Sriram Melkote
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Yes

 Description   
Several users have reported that their views behave differently in 3.x than they did in 2.x in the forums. They've worked out that changing the inclusive_end gets closer to the older behavior.

Notably, these forum postings:
https://forums.couchbase.com/t/view-returns-nothing-when-a-key-is-specified-couchbase-3-0-nodejs-sdk-2-0/1856/1
https://forums.couchbase.com/t/unable-to-query-a-view-by-key-on-3-0-0-on-macos/1783




[MB-12445] view docs incorrectly state that disk persistence is required for values to be indexed Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Cihan Biyikoglu Assignee: Ruth Harris
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
http://docs.couchbase.com/admin/admin/Views/views-operation.html
...
Views are updated when the document data is persisted to disk. There is a delay between creating or updating the document, and the document being updated within the view.


should say :
View are updated as the document data is updated in memory. There is a delay between creating or updating the document, and the document being updated within the view.

 Comments   
Comment by Perry Krug [ 24/Oct/14 ]
I think one step further should be "There may be a delay between creating or updating the document and the document being updated within the view depending on the query parameters used"...and then of course link to the relevant developer and SDK pages that describe what those parameters are.
Comment by Ruth Harris [ 24/Oct/14 ]
Fixed. Changed to:

View are updated as the document data is updated in memory.
      There may be a delay between the document being created or updated and the document being updated within the view
      depending on the client-side query parameters.

No separate document and release-specific links implemented.

Note: Changes are published within a day.




[MB-12444] Update 3.0.0 voltron to upgraded ulimit Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: build
Affects Version/s: 3.0
Fix Version/s: 3.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Aleksey Kondratenko Assignee: Chris Hillery
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to MB-11064 Increase default memcached connection... Resolved

 Comments   
Comment by Chris Hillery [ 24/Oct/14 ]
http://review.couchbase.org/#/c/40433/

This was in Couchbase 3.0.0.




[MB-12443] Object values don't sort correctly Created: 24/Oct/14  Updated: 24/Oct/14  Due: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: cbq-DP4
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown




[MB-12442] Docs: no indentation of sub-categories after second level Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Brett Lawson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-10-24 at 9.35.07 AM.png    
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
See attached screenshot. There are a number of examples of this, but clicking "disk storage" underneath "Architecture and Concepts" doesn't indent its sub-items and makes it harder to visualize where the break point is between "tombstone purging" (the last sub category of disk storage) and "shared thread pool" (the next category after disk storage)

 Comments   
Comment by Matt Ingenthron [ 24/Oct/14 ]
Brett, I believe this is what came over in the HTML design from our designer, correct? Could you clarify why Perry is seeing what he is?
Comment by Perry Krug [ 24/Oct/14 ]
I could undestand that the horizontal space becomes an issue, so perhaps we can find a better way of delineating between sub-topics and peer-topics. Color change? Draw a box?
Comment by Brett Lawson [ 24/Oct/14 ]
Because of the fact that the side-bar uses a non-nested depth hierarchy in it's CSS, we must add specific indentations for each depth. I've added 2 additional levels to the docs css overrides.




[MB-12441] Docs: after selecting sub-category, the left-hand nav resets to the top Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: doc-system
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Every time you click a sub-category, the left-hand navigation starts back over at the top. As you're drilling down deeper and deeper, it makes it harder to do so because you have to click, then scroll, then click, then scroll, etc...

 Comments   
Comment by Perry Krug [ 24/Oct/14 ]
This would also help the case where a direct link is provided to a sub-category. Right now, it just shows the left-hand nav from the top-down
Comment by Ruth Harris [ 24/Oct/14 ]
Perry,

I'm not sure what you're talking about. Does this refer to the 3.0 Server/Developer website?
Comment by Ruth Harris [ 24/Oct/14 ]
I see an issue where deeper sub-topics are not indented in the left-nav. Is this what you're seeing?
Comment by Perry Krug [ 24/Oct/14 ]
Yes, the 3.0 Server/Developer docs...

Everytime you drill down further, the page reloads and the left-hand navigation is shown from the very top of its list which means something you drilled into is going to be possibly below the range of the page.
Comment by Ruth Harris [ 24/Oct/14 ]
Re-assigning to Matt since this is a website issue.
Comment by Perry Krug [ 24/Oct/14 ]
As an example...
-Go to http://docs.couchbase.com/admin/admin/Couchbase-intro.html
-Click "Elastic Search plug-in" from the menu
-Click "Installation Introduction" again from the menu
-When the page refreshes (at least on my laptop size screen), the "Installation Introduction" that I just selected is off the bottom of the page and I need to manually scroll the left-hand nav down again in order to drill in further.

This just makes it harder to quickly drill into the menus and if I give someone this link directly (http://docs.couchbase.com/admin/elastic/install-intro.html) then they don't immediately see where it fits in the overall hierarchy without scrolling.

The desired effect would be to have the left-hand nav's focus "follow" the drill-down




[MB-12440] Docs: Search results show just "Couchbase" as title for many results Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-10-24 at 9.04.51 AM.png    
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
See attached screenshot. It seems that the titles of many pages as shown in the search results are just "Couchbase" and makes it a little harder to identify the desired result.

 Comments   
Comment by Matt Ingenthron [ 24/Oct/14 ]
Note this is based, if I recall correctly, on what's in the DITA. Brett can help clarify if needed. We corrected this on a number of pages on the /developer side.
Comment by Ruth Harris [ 24/Oct/14 ]
I looks like the lower level child topics (in the ditamap) don't reflect their parent topics. Isn't this a scripting issue?




[MB-12439] 3.x Docs, no 32bit support for Amazon Linux Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Ian McCloy Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
On 2 pages..
http://docs.couchbase.com/admin/admin/Install/install-platforms.html
http://docs.couchbase.com/admin/admin/Install/RHEL-install-intro.html

It lists the following as supported: Amazon Linux 2013.03 32 and 64 bit Developer and Production

There aren't any Couchbase 3.0 32Bit Linux builds, nor are there any 32bit Amazon AMIs so only 64bit can be supported.




[MB-12438] 3.x Docs, Mozzila is a typo Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Trivial
Reporter: Ian McCloy Assignee: Ruth Harris
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
http://docs.couchbase.com/admin/admin/Install/pre-install.html
http://docs.couchbase.com/admin/admin/Install/install-browsers.html

Should read as Mozilla not Mozzila

 Comments   
Comment by Ruth Harris [ 24/Oct/14 ]
Fixed. Change should be reflected in the next build.




[MB-12437] UI warns setting replica count to zero requires rebalance. Rebalance is grayed out after saving changes Created: 24/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: UI
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Todd Greenstein Assignee: Aleksey Kondratenko
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: CentOS 7, 4 node cluster running 3.0 GA

Triage: Untriaged
Operating System: Centos 64-bit
Is this a Regression?: Unknown

 Description   
When the replica count is changes from 1 to 0, a warning message says "rebalance is required". Once the changes are saved, the rebalance option is grayed out.




[MB-12436] 3.x Docs, OSX Upgrade page wrong section Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Minor
Reporter: Ian McCloy Assignee: Ruth Harris
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
A customer has been confused about upgrading on OSX.

On this page, The upgrade section there's no mention of OSX.
http://docs.couchbase.com/admin/admin/Install/upgrading.html

Under the "Mac OSX Installation" section there's a page on upgrading with OSX,
http://docs.couchbase.com/admin/admin/Install/upgrade-mac.html
this should be in the upgrading section not the installation section.


 Comments   
Comment by Ruth Harris [ 24/Oct/14 ]
Generic upgrading information is in the upgrading section. Platform-specific upgrading is in the Platform-specific section. This organization is by design.
For Mac OS X, there is no upgrading. You have to un-install and install a new release.




[MB-12435] 3.x Docs, broken images and links on Talend connector page Created: 24/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Ian McCloy Assignee: Brett Lawson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
http://docs.couchbase.com/admin/talend/talend.html

2 images on that page don't exist..

http://docs.couchbase.com/admin/talend/images/talend-integrate.png
http://docs.couchbase.com/admin/talend/images/talend-dropdown-menu.png

the link to the PDF is broken
For more information, see the Talend Connector for Couchbase datasheet. >
http://docs.couchbase.com/admin/talend/docs.couchbase.com/prebuilt/pdfs/talend-datasheet

the link the the talend website is broken (has http:// twice)
http://http//www.talend.com/products/big-data



 Comments   
Comment by Todd Greenstein [ 24/Oct/14 ]
Assigning to Bret for Dita/Docs section
Comment by Ruth Harris [ 24/Oct/14 ]
I looked into the following issues from the doc source perspective and the linking is correct.

The Talend folder contains: 1. talend.ditamatp, 2. talend.dita, 3. images folder with the 2 graphics. The link points to "images/[link-name] and displays in my editor.
I fixed this yesterday, so last nights build should have published all of my changes.
The images are in the repository. I'm not sure what the problem is.

http://docs.couchbase.com/admin/talend/talend.html

2 images on that page don't exist..

http://docs.couchbase.com/admin/talend/images/talend-integrate.png
http://docs.couchbase.com/admin/talend/images/talend-dropdown-menu.png
Comment by Brett Lawson [ 24/Oct/14 ]
The issues with the images was related to a builder problem and has been corrected.
The issues with the links was due to incorrect links specified in the dita file.




[MB-12434] REST API for accounting Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: cbq-DP4
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Colm Mchugh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: REST API for accounting
Epic Status: To Do

 Description   
Query nodes provide an API for accounting information, including metrics / stats. This can be used by both NS server and by 3rd-party monitoring or visualization tools.




[MB-12433] N1QL sample apps Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-alpha, cbq-beta
Fix Version/s: cbq-alpha
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Ilam Siva
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: N1QL sample apps
Epic Status: To Do

 Description   
Create compelling apps to showcase N1QL functionality. These should range from simple apps to complex apps. For example, Ravi proposed a CRM app to be defined and developed in conjunction with Sean F., who has a lot of CRM knowledge.




[MB-12432] REST API for clustering Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: cbq-DP4
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Colm Mchugh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: REST API for clustering
Epic Status: To Do

 Description   
Query nodes will provide a full REST API for clustering concerns. This API will be used by standards-based drivers such as the ODBC and JDBC drivers. These drivers will implement cluster-aware smart client functionality.




[MB-12431] REST API for querying Created: 23/Oct/14  Updated: 23/Oct/14  Due: 07/Nov/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: cbq-DP4
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: REST API for querying
Epic Status: To Do

 Description   
Define query REST API. This includes HTTP methods, payloads, authentication, response formats, status codes, ports, URLs, etc.

Implement same.




[MB-12430] Prepared statements Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-alpha, cbq-beta
Fix Version/s: cbq-alpha
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Prepared statements
Epic Status: To Do

 Description   
Prepared statements enable queries to be executed repeatedly without incurring the cost of parsing and planning.




[MB-12429] N1QL error handling Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: None
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: N1QL error handling
Epic Status: To Do

 Description   
Define error codes, messages, levels, structure, policy, and APIs.

Implement same.




[MB-12428] N1QL tutorial Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: None
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: N1QL tutorial
Epic Status: To Do

 Description   
Interactive tutorial that is available online and installed locally with query.

Continue to improve and refine this tutorial with functionality, examples, flow, data sets, narrative, etc.




[MB-12427] N1QL reference manual Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: None
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: N1QL reference manual
Epic Status: To Do

 Description   
Work with PM and tech pubs to produce N1QL reference manual.




[MB-12426] Simba ODBC and JDBC drivers for SQL-92 Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4, cbq-alpha, cbq-beta
Fix Version/s: None
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Simba ODBC and JDBC drivers for SQL-92
Epic Status: To Do

 Description   
Provide APIs, releases, and support for Simba to build ODBC and JDBC drivers for SQL-92.

High-level terms: https://docs.google.com/document/d/1goSj-M7uh_JnF6TbMs1EDu3xnyJwt1YtxMTalMceCFc/edit#heading=h.b6dg10l9aocq




[MB-12425] [windows] bucket failed to restore after offline upgrade from 2.0.0 to 3.0.1-1440 Created: 23/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: installer
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Thuan Nguyen Assignee: Bin Cui
Resolution: Fixed Votes: 0
Labels: windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: windows server 2008 R2 64-bit

Attachments: Zip Archive 12.11.10.145-10232014-1537-diag.zip    
Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Install couchbase server 2.0.0 on one node.
Create default bucket.
Offline upgrade couchbase server from 2.0.0 to 3.0.1-1440
Upgrade failed to restore default bucket back to 3.0.1 version

 Comments   
Comment by Bin Cui [ 24/Oct/14 ]
http://review.couchbase.org/#/c/42421/




[MB-12424] Query command line shell Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-alpha, cbq-beta
Fix Version/s: None
Security Level: Public

Type: Epic Priority: Major
Reporter: Gerald Sangudi Assignee: Isha Kandaswamy
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Query command line shell
Epic Status: To Do

 Description   
Enhance the cbq command line shell into a best of breed database shell based on best practices in functionality and design across both traditional and emerging databases.

Initial design doc by @colm is here: https://docs.google.com/document/d/10UeZ5NMdHPhUoJjiefhDgLIL83IAU71M_IXXi6T_taQ/edit




[MB-12423] Implement a dynamic thread count tuning mechanism to auto-adjust to changes in workload patterns. Created: 22/Oct/14  Updated: 23/Oct/14

Status: Reopened
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 3.0.1
Fix Version/s: techdebt-backlog
Security Level: Public

Type: Task Priority: Major
Reporter: Venu Uppalapati Assignee: Sundar Sridharan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Currently, we need to manually use cbepctl to vary the thread count distribution among reader/writer tasks. We need a dynamic tuning mechanism that handles this by profiling the current workload being applied and adjust the thread counts.

 Comments   
Comment by Chiyoung Seo [ 23/Oct/14 ]
Please don't use CBD ticket type for this. MB ticket should be used for all kinds of tasks instead.
Comment by Venu Uppalapati [ 23/Oct/14 ]
moved ticket from CBD to MB




[MB-12422] [windows 2012 R2] Couchbase has crashes after installation Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Parag Agarwal Assignee: Aleksey Kondratenko
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: windows 2012 r2, 3.0.1-1440

Triage: Untriaged
Link to Log File, atop/blg, CBCollectInfo, Core dump: https://s3.amazonaws.com/bugdb/jira/MB-12422/172.23.106.34-10232014-1313-diag.zip
Is this a Regression?: Unknown

 Description   
Couchbase has crashes after installation

cannot connect to localhost:8091, seeing erlang crashes

 Comments   
Comment by Aleksey Kondratenko [ 23/Oct/14 ]
It's caused by inability of erlang to spawn it's external port program that performs name resolution:

[error_logger:error,2014-10-23T13:15:49.857,nonode@nohost:error_logger<0.6.0>:ale_error_logger_handler:do_log:203]
=========================SUPERVISOR REPORT=========================
     Supervisor: {local,kernel_safe_sup}
     Context: child_terminated
     Reason: {eacces,
                     [{erlang,open_port,
                          [{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],
                          []},
                      {inet_gethost_native,do_open_port,2,
                          [{file,"inet_gethost_native.erl"},{line,400}]},
                      {inet_gethost_native,server_init,2,
                          [{file,"inet_gethost_native.erl"},{line,183}]}]}
     Offender: [{pid,<0.214.0>},
                  {name,inet_gethost_native_sup},
                  {mfargs,{inet_gethost_native,start_link,undefined}},
                  {restart_type,temporary},
                  {shutdown,1000},
                  {child_type,worker}]
Comment by Parag Agarwal [ 23/Oct/14 ]
Alk/Dave,

172.23.106.43 has issues after uninstall of 1440, reboot and install 1421. The box which I initially referred to seems have been shut down. So I tried on 172.23.106.43, which had similar issues.

The build 1440 works fine as you can observe in sanity tests: 172.23.107.90. This implies that issue isolated to those set of VMs

Comment by Parag Agarwal [ 23/Oct/14 ]
fails for 1402 as well
Comment by Ray Chin [ 23/Oct/14 ]
After disabling ipv6 and rebooting the vm it seems the process can bind to the port. The windows 2012 template we use enables both ipv6 and ipv4 by default.




[MB-12421] [windows 2012 R2] cluster hang after create default bucket Created: 23/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Test Blocker
Reporter: Thuan Nguyen Assignee: Sriram Ganesan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: windows 2012 R2

Triage: Untriaged
Operating System: Windows 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump: cbcollectinfo
http://cbfs.hq.couchbase.com:8484/cbcollect_info/3_0_1/4-nodes-cluster-hang_301_1440.tar
Is this a Regression?: Yes

 Description   
Install couchbase server 3.0.1-1440 on 4 nodes windows server 2012 R2
Create 4 nodes cluster.
Create default bucket. Cluster hang

Cluster info
1:172.23.107.90
2:172.23.107.91
3:172.23.107.92
4:172.23.107.93

Cluster is in hang state now


 Comments   
Comment by Thuan Nguyen [ 23/Oct/14 ]
bug could be reproduced by this test on windows 2012 R2 64-bit
python testrunner.py -i win2012r2-4-sannity.ini -t view.viewquerytests.ViewQueryTests.test_employee_dataset_all_queries -p limit=1000,docs-per-day=2,wait_persistence=true

This test passed on windows 2008 R2 64-bit
Comment by Sriram Ganesan [ 23/Oct/14 ]
From the ns_server logs, it looks like the suspect node is 172.23.107.91. In all other nodes, warmup seems to have completed. There is a plethora of "unable to connect to memcached" errors. Not sure as to why the process is unresponsive. There is no indication that warmup has completed on that node. It might be useful to get some kind of dump from the hung process (assuming that there are symbol files available). Toy builds for windows could help track down the problem but it seems that the current windows toy builds are blocked by https://www.couchbase.com/issues/browse/CBD-1444. Can you provide username/password information for the nodes?

Thanks
Sriram




[MB-12420] possible memory leak Created: 23/Oct/14  Updated: 24/Oct/14

Status: Open
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Matt Ingenthron Assignee: Abhinav Dangeti
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Windows Server 2012 and CentOS

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Unknown

 Description   
User reports memory usage growing substantially with 3.0.1-beta. Looks like a memory leak.

Details here:
https://forums.couchbase.com/t/possible-memory-leak-windows-v3-01/1814

 Comments   
Comment by Matt Ingenthron [ 24/Oct/14 ]
Note that in the forum thread, another user has reported this on a different platform.
Comment by Matt Ingenthron [ 24/Oct/14 ]
possibly related to MB-12447?




[MB-12419] stale=false view performance up to 10x slower than stale=ok or stale=update_after with no data changing Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Sriram Melkote
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
I have a very basic case where I am trying to understand the performance difference between the various stale options. I've created the beer-sample bucket and have no incoming workload.

Running this command:
for i in `seq 1 1000`; do curl "http://ec2-54-176-27-210.us-west-1.compute.amazo
naws.com:8092/beer-sample/_design/beer/_view/brewery_beers?inclusive_end=false&s
tale=update_after&connection_timeout=60000&limit=1&skip=0" > /dev/null 2> /dev/n
ull; done

Yields about 80 view requests/sec.

Changing that to stale=false gets only about 9 or 10 view requests/sec.

With 2.5.1, they are almost identical.

So two questions:
-Is this difference in performance to be expected?
-Is there any tuning or profiling I can do to improve it?




[MB-12418] Limit stack trace to the panicking goroutine Created: 23/Oct/14  Updated: 23/Oct/14  Due: 27/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: cbq-DP4
Security Level: Public

Type: Improvement Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
For improved debugging and readability, the stack stack trace after a panic should be limited to the panicking go routine.




[MB-12417] cbbackup runs out of resources while backing up large DBs. Created: 23/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: tools
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: adonoho Assignee: Bin Cui
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: OS X Mavericks, 10.9.5, CBServer Version: 3.0.0 Enterprise Edition (build-1209-rel)

Triage: Untriaged
Operating System: MacOSX 64-bit
Is this a Regression?: Unknown

 Description   
When backing up a large DB from CB server, cbbackup exhausts the resources of the backing up machine. The DB in question has 124 million documents and is 218 GB in size. The machine doing the backing up is only running cbbackup and has 16 GB of RAM and is writing to a large attached drive with roughly three times the available free space as the source DB. I have tried the backup twice and the first time the OS protected itself by pausing the backup process. The second time it just locked up. In both cases, the database had saved only 32.6% and 35.3%, respectively. On the second attempt, I was hoping that the backup would pick up where it left off. Instead it appears to have ignored the versions of the already saved documents and written them again … and crashed at about the same point. The CBServer machine was unaffected by the lockup but I've restarted it to be safe.

It would be quite weird to require that a machine doing the backups be as powerful as the CBServer cluster.

I would very much like to back this data up. It takes days to insert this much data into CBServer. With server 2.5.1, it takes roughly 8 hours to backup and restore this data. Then the view calculations kick in. In other words, this is a critical feature.




[MB-12416] 3.0.1 node does not take over master in online upgrade from 3.0.0 to 3.0.1 Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Thuan Nguyen Assignee: Aleksey Kondratenko
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive 12.11.10.131-10222014-1631-diag.zip    
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Install couchbase server 3.0.0 on 2 nodes (130 and 131)
Install couchbase server 3.0.1-1437 on node 132
Create a 3.0.0 cluster (130 and 131)
Add node 3.0.1 (132) to 3.0.0 cluster.
Node 3.0.1 does not take over master from old version nodes
Remove node 131 (swap rebalance)
Rebalance. Passed

 Comments   
Comment by Thuan Nguyen [ 22/Oct/14 ]
Jira could not attach the second and third collectinfo files. I will put them in cbfs
Comment by Thuan Nguyen [ 22/Oct/14 ]
http://cbfs.hq.couchbase.com:8484/cbcollect_info/3_0_1/unix/2014_10/12.11.10.130-10222014-1630-diag.zip
http://cbfs.hq.couchbase.com:8484/cbcollect_info/3_0_1/unix/2014_10/12.11.10.132-10222014-1632-diag.zip




[MB-12415] Convert _run.go xdcr integration test files to _test.go to perform code coverage Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: sherlock
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Aruna Piravi Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: XDCR next release

 Description   
Repo - Xiaomei-Zhang/couchbase_goxdcr_impl




[MB-12414] Write unit tests for packages in https://github.com/Xiaomei-Zhang/couchbase_goxdcr_impl Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: sherlock
Fix Version/s: None
Security Level: Public

Type: Task Priority: Critical
Reporter: Aruna Piravi Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: xdc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: XDCR next release




[MB-12413] select count(column) is it expected to work? Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
- create primary index
- select count(*) - works as expected.

- select count(city) from `beer-sample ` - does nothing, no error, no results, the query simply hangs
select COUNT(city) from `beer-sample`;
{
    "signature": {
        "$1": "number"
    },
    "results"

- select count(nested path to city) from `beer-sample` - likewise behaviour.

Is the above expected to work w/ n1ql? or do we only support "select count(*) "






[MB-12412] Information on describing indexes for n1ql Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
If a user needs to find out information on indexes mapped to which column, is there a way for user to do so?

I could not find out information on this based on couchbaselabs/query docs.

This is what I was doing
select * from system:indexes;
      {
            "indexes": {
                "id": "#primary",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "beer-sample",
                "name": "#primary",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
      
      "indexes": {
                "id": "new_index",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "beer-sample",
                "name": "new_index",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        }
    ],
    "state": "success",
    "metrics": {
        "elapsedTime": "1.954704ms",
        "executionTime": "1.861035ms",
        "resultCount": 8
    }


The output does not contain information on "index_key" and I am not able to use this further for queries for example
- select * from table USE KEYS ...

  




[MB-12411] Reverse ordering on Select stmt, ie from- select -where does not work Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Yes

 Description   
1. load beer-sample bucket
2. Create primary index on the bucket, (It will not work else)
3. Run queries like
a. cbq> from `beer-sample` select DISTINCT country where code=94107;
syntax error

the exact same query with regular syntax works
cbq> select DISTINCT country from `beer-sample` where code=94107;
{
    "signature": {
        "country": "json"
    },
    "results": [
    ],
    "state": "success",
    "metrics": {
        "elapsedTime": "10.350356056s",
        "executionTime": "10.350331985s",
  




[MB-12410] [mac] ntohll not defined in /usr/include/sys/_endian.h Created: 22/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: None
Affects Version/s: .master
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Abhinav Dangeti Assignee: Abhinav Dangeti
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
With Xcode 6.1 and mavericks:

find /usr/include | xargs grep ntohll 2>/dev/zero
"no results"

Error during compiling:
/Users/abhinavdangeti/Documents/couchbaseA/couchstore/src/couch_db.cc:600:16: error: use of undeclared identifier 'htonll'; did you mean 'atoll'

Caused by this change, in platform:
+#if __apple_build_version__ >= 6000054
+#define CB_DONT_NEED_BYTEORDER 1
+#endif


 Comments   
Comment by Jim Walker [ 23/Oct/14 ]
 http://review.couchbase.org/#/c/42381/
Comment by Trond Norbye [ 23/Oct/14 ]
Please verify that the fix work for you...




[MB-12409] n1ql error messages should be more verbose Created: 22/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
For example, running different queries today, return a standard error " syntax error".

There is no way for user's to know the correct documentation or correct the syntactical query.

cbq> drop index idx1;
syntax error

correct usage: drop index s.idx1

the above is a trivial example, but this occurs across multiple places, where syntax errors is the only output that users can view.






[MB-12408] cbq-engine crashes on select from system:indexes Created: 22/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File crash.rtf    
Triage: Untriaged
Is this a Regression?: Yes

 Description   
cbq> select * from system:indexes;
{
    "signature": {
        "*": "*"
    },
    "results": [

- Run query on system:indexes, returns no results.


 Comments   
Comment by Ketaki Gangal [ 22/Oct/14 ]
On successive runs on system:indexes, howver it appears to run as expected.

cbq> select * from system:indexes;
{
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "indexes": {
                "id": "#primary",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "k123",
                "name": "#primary",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
        {
            "indexes": {
                "id": "idx1",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "k123",
                "name": "idx1",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
        {
            "indexes": {
                "id": "idx2",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "k123",
                "name": "idx2",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
        {
            "indexes": {
                "id": "#primary",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "sabre",
                "name": "#primary",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
        {
            "indexes": {
                "id": "dep_index",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "sabre",
                "name": "dep_index",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        },
        {
            "indexes": {
                "id": "idx2",
                "index_key": [],
                "index_type": "view",
                "keyspace_id": "sabre",
                "name": "idx2",
                "namespace_id": "default",
                "store_id": "http://172.23.107.102:8091"
            }
        }
    ],
    "state": "success",
    "metrics": {
        "elapsedTime": "2.710916ms",
        "executionTime": "2.652113ms",
        "resultCount": 6
    }
}
Comment by Ketaki Gangal [ 22/Oct/14 ]
The order to get this error:

1. create primary index on bucket1
2. On success, select * from system:indexes -- Crash on cbq-engine, attached log

3. On restarting up the cbq-engine, re-running the same command now works.




[MB-12407] XDCR@next release - Code merge to couchbase Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 32h
Time Spent: Not Specified
Original Estimate: 32h

Epic Link: XDCR next release

 Description   
-consider refactor the code to combine two projects to one project.




[MB-12406] XDCR@next release - incorporate with KVFeed's latest code refactoring. Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 40h
Time Spent: Not Specified
Original Estimate: 40h

Epic Link: XDCR next release




[MB-12405] XDCR@next release - performance improvement and tuning Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 32h
Time Spent: Not Specified
Original Estimate: 32h

Epic Link: XDCR next release




[MB-12404] XDCR@next release - performance validation: long running test Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 40h
Time Spent: Not Specified
Original Estimate: 40h

Epic Link: XDCR next release

 Description   
run the replication for >24 hours




[MB-12403] XDCR@next release - Performance validation - replication can scale up to 256 Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 32h
Time Spent: Not Specified
Original Estimate: 32h

Epic Link: XDCR next release




[MB-12402] XDCR@next release - performance validation on the replication latency with continuous replication Created: 22/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Yu Sui
Resolution: Done Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 40h
Time Spent: Not Specified
Original Estimate: 40h

Epic Link: XDCR next release

 Description   
performance validation
case 1: two cluster each with one node, generate continuous load on source, observe the time the document replicated to the target
case 2: two clusters each with 2 nodes, generate continuous load on source, observe the time the document replicated to the target

 Comments   
Comment by Yu Sui [ 24/Oct/14 ]
Test setup:

AWS c3.xlarge instances.

1. one node per cluster
100K docs. 8 source nozzles per node. 4 xmem nozzles per node. 500 write routines. 837 sample_frequency

Average latency:
Async mode: 0.28s
Batch mode: 0.45s
Existing xdcr: 14s

2. two nodes per cluster
100K docs. 4 source nozzles per node. 2 xmem nozzles per node. 500 write routines. 837 sample_frequency

Average latency:
Async mode: 0.28s
Batch mode: 0.3s
Existing xdcr: 6.7s

Async mode is a bit faster than batch mode. Both significantly faster than existing xdcr.




[MB-12401] Provide DP4 scope document for QE and PM Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Gerald Sangudi Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified





[MB-12400] Resolve document lost when replication concurrency is high (>32) Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: feature-backlog
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Xiaomei Zhang Assignee: Xiaomei Zhang
Resolution: Unresolved Votes: 0
Labels: sprint3_xdcr
Remaining Estimate: 24h
Time Spent: Not Specified
Original Estimate: 24h

Epic Link: XDCR next release

 Description   
When concurrency is high (16 KVFeed + 32 Xmem Nozzle), we see documents failed to replicate to target cluster due to one or more TCP socket used by Xmem Nozzle stuck at write.




[MB-12399] 38% regression with Rebalance swap time with view and query workload. Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Yes

 Description   
Test description:
Rebalance-swap (min), 3 -> 3 / 1, 1 bucket x 100M x 2KB, 1 x 1 views, 10K ops/sec, 400 queries/sec

Observation:
swap rebalance time increased from 406.5 min in 2.5.1 to 562.1 min in 3.0.1

links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_498_rebalance
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_c81_rebalance

logs:
http://ci.sc.couchbase.com/job/zeus-64/1230/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1230/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1230/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1230/artifact/172.23.96.28.zip
http://ci.sc.couchbase.com/job/zeus-64/1230/artifact/web_log_172.23.96.25.json

 Comments   
Comment by Nimish Gupta [ 22/Oct/14 ]
This seems to be duplicate of MB-12125.




[MB-12398] Increase logging level of illegal lock timeout message Created: 22/Oct/14  Updated: 23/Oct/14  Resolved: 23/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: memcached
Affects Version/s: 2.5.1, 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Chris Malarky Assignee: Chiyoung Seo
Resolution: Fixed Votes: 0
Labels: ep-engine
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
When a client requests an invalid lock time (greater than max_timeout, less than 1), then default_timeout is used instead and memcached logs this with EXTENSION_LOG_DEBUG.

In production builds we only log EXTENSION_LOG_WARNING so this message disappears, meaning we are silently changing the clients request.

Please change the log level for this message to EXTENSION_LOG_WARNING so that users can see when their requests are being modified.

 Comments   
Comment by Trond Norbye [ 23/Oct/14 ]
http://review.couchbase.org/42387
Comment by Trond Norbye [ 23/Oct/14 ]
I've made a patch. If you don't think we should include it 3.0.1, feel free to move it to sherlock. I'd say the fix is really low risk and would be nice for people to have in case they run into this problem (but a better fix would be to return ERANGE for invalid values and have the client deal with it.. With the current behavior the client thinks it has a lock for the object in a different time than it actually have...)
Comment by Abhinav Dangeti [ 23/Oct/14 ]
Merged into 3.0.1.




[MB-12397] couchbase-cli tool Does not have a list of commands below. Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Patrick Varley Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://docs.couchbase.com/admin/admin/CLI/cbcli-intro.html


 Description   
The cbcli-intro (http://docs.couchbase.com/admin/admin/CLI/cbcli-intro.html) suggest that there is a list of commands below:

COMMAND is a command listed below.

The commands have been move to another page, we should link to them:

COMMAND is a command listed [here](http://docs.couchbase.com/admin/admin/CLI/CBcli/cbcli-commands.html)




[MB-12396] Projector continues to retry UPR Connection even after deletion of a bucket with secondary index(es) Created: 22/Oct/14  Updated: 22/Oct/14

Status: Open
Project: Couchbase Server
Component/s: secondary-index
Affects Version/s: sherlock
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Prathibha Bisarahalli Assignee: Sriram Melkote
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Create a bucket and 2i in it.
Delete the bucket.

From projector logs, we can see that it is continuing to retry connection with the bucket -

2014/10/22 15:36:43 go-couchbase: Error connecting to upr feed of 127.0.0.1:12000: MCResponse status=0x20, opcode=SASL_AUTH, opaque=0, msg: Auth failure
2014/10/22 15:36:43 go-couchbase: Error connecting to upr feed of 127.0.0.1:12000: MCResponse status=0x20, opcode=SASL_AUTH, opaque=0, msg: Auth failure
2014/10/22 15:37:13 go-couchbase: UPR connection lost; reconnecting to bucket "test1" in 30s
2014/10/22 15:37:13 go-couchbase: UPR connection lost; reconnecting to bucket "test1" in 30s
2014/10/22 15:37:13 Unable to refresh bucket HTTP error 404 Object Not Found getting "http://127.0.0.1:9001/pools/default/buckets/test1?bucket_uuid=b47791fa38e35cda4e0ea4e7d4ad9ceb": Requested resource not found.
 
2014/10/22 15:37:13 Unable to refresh bucket HTTP error 404 Object Not Found getting "http://127.0.0.1:9001/pools/default/buckets/test1?bucket_uuid=b47791fa38e35cda4e0ea4e7d4ad9ceb": Requested resource not found.





Test Automation Advancements for Sherlock (MB-12223)

[MB-12395] Generate test reports with possible security weaknesses for Forest DB Created: 21/Oct/14  Updated: 21/Oct/14

Status: Open
Project: Couchbase Server
Component/s: test-execution
Affects Version/s: sherlock
Fix Version/s: sherlock
Security Level: Public

Type: Technical task Priority: Major
Reporter: Raju Suravarjjala Assignee: Tommie McAfee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I have found this tool which might help us in finding possible security weakness in Forest db http://www.dwheeler.com/flawfinder/

If you know of a better tool, feel free to use that one instead




Test Automation Advancements for Sherlock (MB-12223)

[MB-12394] Code coverage report for secondary index tests Created: 21/Oct/14  Updated: 21/Oct/14

Status: Open
Project: Couchbase Server
Component/s: test-execution
Affects Version/s: sherlock
Fix Version/s: sherlock
Security Level: Public

Type: Technical task Priority: Major
Reporter: Raju Suravarjjala Assignee: Parag Agarwal
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified





[MB-12393] 'explain' stmt does not generated expected explain output Created: 21/Oct/14  Updated: 21/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: 2.5.0, 3.0, sherlock
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: * longevity cluster.

Triage: Untriaged
Is this a Regression?: Yes

 Description   
1. Create bucket here http://172.23.107.102:8091
2. Couchbase version 2.5.X
3. pull latest code from github/query
4. Create Primary Index on bucket
4. Run stmt for EXPLAIN - I expect it to show IndexScan/ Fetch or any plan information on what was selected but the resultset does not contain any valuable information.

What is the expected output from EXPLAIN with n1ql?

cbq> EXPLAIN select * from `sCustomer`;
{
    "signature": "json",
    "results": [
    ],
    "state": "success",
    "metrics": {
        "elapsedTime": "696.153us",
        "executionTime": "633.554us",
        "resultCount": 0
    }
}







[MB-12392] Update current readme on github/query to include steps to setup the cbq-engine Created: 21/Oct/14  Updated: 21/Oct/14

Status: In Progress
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0, sherlock
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Currently the readme does not contain setup steps for the cbq-engine https://github.com/couchbaselabs/query/blob/master/README.md

It would be nice to have something like https://github.com/couchbaselabs/tuqtng/blob/master/README.md

for detailed instructions on env variables, package dependencies during the setup.






[MB-12391] Cannot start indexer or projector due to dependency on forestdb:: : libforestdb.so: cannot open shared object file: Created: 21/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: secondary-index
Affects Version/s: sherlock
Fix Version/s: sherlock
Security Level: Public

Type: Bug Priority: Test Blocker
Reporter: Parag Agarwal Assignee: Chris Hillery
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: centos 6x, Version: 3.5.0 Enterprise Edition (build-18)


Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Installed latest sherlock build and tried to run indexer and projector

[root@palm-10307 bin]# ./projector --help
./projector: error while loading shared libraries: libforestdb.so: cannot open shared object file: No such file or directory
[root@palm-10307 bin]# ./indexer --help
./indexer: error while loading shared libraries: libforestdb.so: cannot open shared object file: No such file or directory
[root@palm-10307 bin]# ./indexer
./indexer: error while loading shared libraries: libforestdb.so: cannot open shared object file: No such file or directory
[root@palm-10307 bin]# ./projector -debug localhost:9001 -kvaddrs="127.0.0.1:12002”
> -bash: unexpected EOF while looking for matching `"'
-bash: syntax error: unexpected end of file
[root@palm-10307 bin]# ./projector -debug localhost:9001 -kvaddrs="127.0.0.1:12002"
./projector: error while loading shared libraries: libforestdb.so: cannot open shared object file: No such file or directory
[root@palm-10307 bin]#

 Comments   
Comment by Sarath Lakshman [ 22/Oct/14 ]
We need to provide rpath while building indexer using cgo libraries.

Here is the corresponding change:
https://github.com/t3rm1n4l/indexing-build-scripts/commit/981ac7379f4bc58d5f885427f4a6a5e744be7378
Comment by Sarath Lakshman [ 22/Oct/14 ]
Ceej, it would be great if you could fix this problem in your toy build.
Comment by Chris Hillery [ 23/Oct/14 ]
This is actually a really ugly problem. The fix proposed above will only work on Linux with gcc, I'm betting. We limit ourselves to that compiler by using LDFLAGS that way. On a Mac, "RPATH" is handled quite differently, and of course on Windows there's no equivalent concept at all.

CMake has some pretty extensive support for bending RPATH to your will, but it depends on being able to manage the compile and link steps itself as well as the install step. Since it doesn't have built-in support for Go, it can't work its magic.

I'm searching around for other solutions that will be more cross-compiler and cross-platform. (Why did Google have to pick a name for their language that is so hard to Google for?)




[MB-12390] select count(*) fails for any bucket if no explicit primary index is defined Created: 21/Oct/14  Updated: 22/Oct/14

Status: In Progress
Project: Couchbase Server
Component/s: query
Affects Version/s: 3.0, sherlock
Fix Version/s: cbq-DP4
Security Level: Public

Type: Bug Priority: Critical
Reporter: Ketaki Gangal Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Centos 64-bit
Is this a Regression?: Unknown

 Description   
1.install couchbase 3.0 or 3.5
2. build.sh
3../server/main/cbq-engine -datastore http://10.1.3.176:8091
4. startup shell/cbq client

5. Run query like
cbq> select COUNT(*) from beer-sample;
syntax error

 select COUNT(*) from k0;
{
    "signature": {
        "$1": "number"
    },
    "results": [
        {
            "$1": 0
        }
    ],
    "errors": [
        {
            "caller": "couchbase:288",
            "code": 5000,
            "key": "Internal Error",
            "message": "No primary index found. Please create a primary index on bucket k0"
        }
    ],
    "state": "errors",
    "metrics": {
        "elapsedTime": "165.025808ms",
        "executionTime": "164.982529ms",
        "resultCount": 1,
        "errorCount": 1
    }
}

cbq> select COUNT(*) from b0;
{
    "signature": {
        "$1": "number"
    },
    "results": [
        {
            "$1": 1
        }
    ],
    "state": "success",
    "metrics": {
        "elapsedTime": "45.460007ms",
        "executionTime": "45.372988ms",
        "resultCount": 1
    }
}

Is Count not expected to work if primary indexes are not defined?


 Comments   
Comment by Gerald Sangudi [ 21/Oct/14 ]
select count(*) from `beer-sample`

should avoid the syntax error (hyphen in bucket name).

select count(*) should not require a primary key; will investigate.
Comment by Ketaki Gangal [ 21/Oct/14 ]
ok. Though now I get this error
cbq> select COUNT(*) from `beer-sample`;
{
    "signature": {
        "$1": "number"
    },
    "results": [
        {
            "$1": 0
        }
    ],
    "errors": [
        {
            "caller": "couchbase:288",
            "code": 5000,
            "key": "Internal Error",
            "message": "No primary index found. Please create a primary index on bucket beer-sample"
        }
    ],
    "state": "errors",
    "metrics": {
        "elapsedTime": "49.775952ms",
        "executionTime": "49.750593ms",
        "resultCount": 1,
        "errorCount": 1
    }
}





[MB-12389] Deletion of a field in a document does not result in secondary index being updated Created: 21/Oct/14  Updated: 21/Oct/14

Status: Open
Project: Couchbase Server
Component/s: secondary-index
Affects Version/s: sherlock
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Critical
Reporter: Prathibha Bisarahalli Assignee: Deepkaran Salooja
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: No

 Description   
When there is a 2i created on a field, and the field is deleted from one or more documents, this mutation is not updated in the index. On querying for those field values, the documents are still returned by the query.

Repro:
1. Create a bucket with documents with field say, "State". Create 2i on State.
2. Delete the "State" field from one of the documents.
3. Query for the State with value that was deleted. The query still returns the document from which State field was removed.

In this case, the indexer just logs the error :

 [ERROR] Flusher::processUpsert Error Generating KeyFrom Mutation: [[]]. Skipped. Error: unexpected end of JSON input

and skips updating the index for the deleted field.

 Comments   
Comment by Deepkaran Salooja [ 21/Oct/14 ]
Collatejson is returning error for nil keys:
[ERROR] Flusher::processUpsert Error Generating KeyFrom Mutation: [[]]. Skipped. Error: unexpected end of JSON input

Will take this issue up when we revisit the key storage format in next sprint.




[MB-12388] Admin UI: Everywhere we should the release version, show the build number in close proximity Created: 20/Oct/14  Updated: 21/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.5.1
Fix Version/s: 2.5.1, 3.0.1, sherlock
Security Level: Public

Type: Task Priority: Critical
Reporter: Dave Finlay Assignee: Dave Finlay
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This was cloned from the parent issue: http://www.couchbase.com/issues/browse/MB-12387 to track the needed fixes in ns_server.

--------------------------

The build number is a critical piece of information to understand precisely what version of Couchbase server is running at the customer site.

E.g. For 2.5.1 we have released a maintenance pack. The MP has a different build number than vanilla 2.5.1 but the build number is not prominently displayed in close proximity to the release version, so customers and support who are working with the customer may incorrectly deduce the exact release version and build the customer is on.

To fix this, we propose to append the build number with a dash everywhere the release version shows.
E.g. instead of plain 2.5.1 we should show 2.5.1-1083 (for vanilla 2.5.1) and 2.5.1-1100 (for MP1.)


 




[MB-12387] Everywhere we should the release version, show the build number in close proximity Created: 20/Oct/14  Updated: 20/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 2.5.1
Fix Version/s: 2.5.1
Security Level: Public

Type: Task Priority: Critical
Reporter: Dave Finlay Assignee: Dave Finlay
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
The build number is a critical piece of information to understand precisely what version of Couchbase server is running at the customer site.

E.g. For 2.5.1 we have released a maintenance pack. The MP has a different build number than vanilla 2.5.1 but the build number is not prominently displayed in close proximity to the release version, so customers and support who are working with the customer may incorrectly deduce the exact release version and build the customer is on.

To fix this, we propose to append the build number with a dash everywhere the release version shows.
E.g. instead of plain 2.5.1 we should show 2.5.1-1083 (for vanilla 2.5.1) and 2.5.1-1100 (for MP1.)

This issue is meant to be the uber task to which we'll attach individual issues to track the various places things need to be fixed.

ns_server: http://www.couchbase.com/issues/browse/MB-12388

 




[MB-12386] put 3.0.1 windows latest build in 3.0.1 section Created: 20/Oct/14  Updated: 20/Oct/14

Status: Open
Project: Couchbase Server
Component/s: build
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Improvement Priority: Critical
Reporter: Thuan Nguyen Assignee: Chris Hillery
Resolution: Unresolved Votes: 0
Labels: windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: windows


 Description   
Please add one more url link for windows latest build in 3.0.1 section in
http://latestbuilds.hq.couchbase.com/




[MB-12385] unable to add back the node referenced by hostname Created: 20/Oct/14  Updated: 21/Oct/14  Resolved: 21/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Iryna Mironava Assignee: Iryna Mironava
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: 3.0.1-1419

Triage: Untriaged
Operating System: Ubuntu 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump: https://s3.amazonaws.com/bugdb/jira/MB-12385/c488aa56/172.23.107.24-10202014-1059-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-12385/c488aa56/172.23.107.25-10202014-111-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-12385/c488aa56/172.23.107.26-10202014-110-diag.zip
Is this a Regression?: Yes

 Description   
-t hostname.hostnamemgmt_tests.HostnameMgmtTests.test_rename_failover_add_back

3 nodes refenrenced by hostname are in cluster
failover one of them and add back. Error appears
2014-10-20 10:58:49 | ERROR | MainProcess | test_thread | [rest_client.add_back_node] add_back_node ns_1@cherry-s10120.sc.couchbase.com error : {"otpNode":"invalid node name or node can't be used for delta recovery"}

attaching cbcollects

 Comments   
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
We've recently fixed MB-7226 and otpNode parameter is now validated. When previously it would just ignore errors.

So this is likely some previously undiscovered bug in testrunner. Check your code for exactly what is being POST-ed.
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
I'm not seeing anything suspicious in logs. And I'm certain that reAddNode works. I've just re-tested it myself.

So I'm certain it must be something in the test that wasn't previously spotted. Consider logging everything you're doing so that it's seen what exactly fails and why.




[MB-12384] append and prepend commands to support TTL Created: 20/Oct/14  Updated: 23/Oct/14

Status: Open
Project: Couchbase Server
Component/s: memcached
Affects Version/s: 2.5.1
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Patrick Varley Assignee: Trond Norbye
Resolution: Unresolved Votes: 0
Labels: customer, greenstack
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency

 Description   
Currently the memcached binary protocol does not support the TTL field on append and prepend operations.

https://code.google.com/p/memcached/wiki/BinaryProtocolRevamped#Append,_Prepend

It would be useful to update the TTL at the same time as executing the command.

 Comments   
Comment by Trond Norbye [ 23/Oct/14 ]
This won't happen until project Greenstack is implemented (post sherlock).




[MB-12383] on windows server 3.0, failures to flush Created: 20/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Simon Baslé Assignee: Aleksey Kondratenko
Resolution: Duplicate Votes: 0
Labels: windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: dev workstation, windows 7-64bits, quad-core, 8GB RAM (including 700MB couchbase quota), Couchbase Server 3.0.1 Enterprise Edition (build-1323-rel)

Attachments: Zip Archive logs_flush_failure.zip    
Issue Links:
Duplicate
duplicates MB-6232 ep-engine needs 1.5 minutes to create... Reopened
Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Unknown

 Description   
When trying to run tests with the Java SDK, I have some flush operations. The server returns {error,{flush_wait_failed,['ns_1@127.0.0.1'],[]}} ...

There is only the default bucket, which is empty and is assigned 256MB of the cluster's RAM quota of 700MB (this is a dev workstation and I have lots of ram consumed by other tools, hence the low quotas).

When trying to flush from webconsole, I also often get an error : "Save request failed because of timeout."

Logs from a clean start of the server with only previous two issues reproducted will be attached.

 Comments   
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
This is likely our old friend MB-6232.

Workaround should be same as on GNU/Linux.

Windows equivalent can be reached via drive settings. As can be seen on this screen-shot:

http://i.imgur.com/wHAx3BF.png

You should (at least just for test) check "turn off Window write-cache buffer flushing".

I'm not sure if it's going to be enough or not. Please try.
Comment by Simon Baslé [ 20/Oct/14 ]
seems like it works with the buffer turned off...
not really confortable doing it on my desktop (no battery power to prevent power outage failures, etc...) but I can activate it during tests and look into alternatives on where to run my test server for the future
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
Making it duplicate of MB-6232 then.

You can use VM where it's less risky to disable cache flushing. Also lowering number of vbuckets is known to help quite a lot. MB-6232 should have all instructions for that.




[MB-12382] Offline cluster upgrade failed 2.0.1-170-rel -> 3.0.1-1422-rel Created: 20/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Sangharsh Agarwal Assignee: Sangharsh Agarwal
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Os: CentOS

Triage: Untriaged
Operating System: Centos 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump: 10.1.3.93 : https://s3.amazonaws.com/bugdb/jira/MB-12382/91882dce/10.1.3.93-diag.txt.gz
10.1.3.93 : https://s3.amazonaws.com/bugdb/jira/MB-12382/daf32985/10.1.3.93-10182014-1830-diag.zip
10.1.3.94 : https://s3.amazonaws.com/bugdb/jira/MB-12382/23591591/10.1.3.94-diag.txt.gz
10.1.3.94 : https://s3.amazonaws.com/bugdb/jira/MB-12382/753549fa/10.1.3.94-10182014-1831-diag.zip
Is this a Regression?: Yes

 Description   
Connection to Memcached is dropped after offline upgrade.

Offline upgrade 10.1.3.93 and 10.1.3.94 is failed.

[ns_server.babysitter.log]
[ns_server:info,2014-10-18T18:14:04.214,babysitter_of_ns_1@127.0.0.1:<0.78.0>:ns_port_server:log:181]memcached<0.78.0>: Invalid value specified for verbosity: []
memcached<0.78.0>:
memcached<0.78.0>: Terminating

[ns_server:info,2014-10-18T18:14:04.214,babysitter_of_ns_1@127.0.0.1:<0.77.0>:supervisor_cushion:handle_info:58]Cushion managed supervisor for memcached failed: {abnormal,1}
[ns_server:info,2014-10-18T18:14:04.214,babysitter_of_ns_1@127.0.0.1:<0.77.0>:supervisor_cushion:die_slowly:80]Service memcached exited on node 'babysitter_of_ns_1@127.0.0.1' in 0.08s

[error_logger:error,2014-10-18T18:14:04.215,babysitter_of_ns_1@127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:do_log:203]** Generic server <0.78.0> terminating
** Last message in was {#Port<0.3398>,{exit_status,1}}
** When Server state == {state,#Port<0.3398>,memcached,
                               {["Terminating",[],
                                 "Invalid value specified for verbosity: []",
                                 empty],
                                [empty]},
                               {ok,{1413681244413,#Ref<0.0.0.280>}},
                               ["Terminating",[],
                                "Invalid value specified for verbosity: []"],
                               0,true}
** Reason for termination ==
** {abnormal,1}

[error_logger:error,2014-10-18T18:14:04.221,babysitter_of_ns_1@127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:do_log:203]
=========================CRASH REPORT=========================
  crasher:
    initial call: ns_port_server:init/1
    pid: <0.78.0>
    registered_name: []
    exception exit: {abnormal,1}
      in function gen_server:terminate/6 (gen_server.erl, line 744)
    ancestors: [<0.77.0>,ns_child_ports_sup,ns_babysitter_sup,<0.56.0>]
    messages: [{'EXIT',#Port<0.3398>,normal}]
    links: [<0.77.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 1598
    stack_size: 27
    reductions: 1025
  neighbours:


[Server Error]
[ns_server:info,2014-10-18T18:13:54.416,ns_1@10.1.3.93:ns_config<0.262.0>:ns_config_default:upgrade_config_from_2_0_to_2_2_0:623]Upgrading config from 2.0 to 2.2.0
[ns_server:info,2014-10-18T18:13:54.420,ns_1@10.1.3.93:ns_config<0.262.0>:ns_config_default:upgrade_config_from_2_2_0_to_2_3_0:630]Upgrading config from 2.2.0 to 2.3.0
[ns_server:info,2014-10-18T18:13:54.421,ns_1@10.1.3.93:ns_config<0.262.0>:ns_config_default:upgrade_config_from_2_3_0_to_3_0:644]Upgrading config from 2.3.0 to 3.0
[ns_server:info,2014-10-18T18:13:54.426,ns_1@10.1.3.93:ns_config<0.262.0>:ns_config_default:upgrade_config_from_3_0_to_3_0_1:680]Upgrading config from 3.0 to 3.0.1
[ns_server:info,2014-10-18T18:13:54.552,ns_1@10.1.3.93:ns_server_sup<0.271.0>:dir_size:start_link:49]Starting quick version of dir_size with program name: i386-linux-godu
[ns_server:warn,2014-10-18T18:13:54.596,ns_1@10.1.3.93:ns_config_isasl_sync<0.279.0>:ns_memcached:connect:1260]Unable to connect: {error,{badmatch,{error,econnrefused}}}, retrying.
[user:info,2014-10-18T18:13:55.602,ns_1@10.1.3.93:ns_cookie_manager<0.257.0>:ns_cookie_manager:do_cookie_sync:130]Node 'ns_1@10.1.3.93' synchronized otp cookie pcpsknplpzdwdovs from cluster
[ns_server:info,2014-10-18T18:13:55.632,ns_1@10.1.3.93:ns_config_rep<0.296.0>:ns_config_rep:do_pull:343]Pulling config from: 'ns_1@10.1.3.94'

[user:info,2014-10-18T18:14:04.109,ns_1@10.1.3.93:ns_server_sup<0.271.0>:menelaus_sup:start_link:44]Couchbase Server has started on web port 8091 on node 'ns_1@10.1.3.93'. Version: "3.0.1-1422-rel-enterprise".
[ns_server:info,2014-10-18T18:14:04.135,ns_1@10.1.3.93:<0.433.0>:ns_memcached_log_rotator:init:28]Starting log rotator on "/opt/couchbase/var/lib/couchbase/logs"/"memcached.log"* with an initial period of 39003ms
[user:info,2014-10-18T18:14:04.214,ns_1@10.1.3.93:<0.278.0>:ns_log:crash_consumption_loop:70]Port server memcached on node 'babysitter_of_ns_1@127.0.0.1' exited with status 1. Restarting. Messages: Invalid value specified for verbosity: []

Terminating
[ns_server:warn,2014-10-18T18:14:04.293,ns_1@10.1.3.93:<0.488.0>:ns_memcached:connect:1260]Unable to connect: {error,{badmatch,{error,econnrefused}}}, retrying.
[ns_server:warn,2014-10-18T18:14:04.305,ns_1@10.1.3.93:<0.500.0>:ns_memcached:connect:1260]Unable to connect: {error,{badmatch,{error,econnrefused}}}, retrying.



[Test]
./testrunner -i INI_FILE.ini get-cbcollect-info=True,get-logs=False,stop-on-failure=False,get-coredumps=True,upgrade_version=${version_number},GROUP=ALL,upgrade_version=3.0.1-1422-rel -t xdcr.upgradeXDCR.UpgradeTests.offline_cluster_upgrade,initial_version=2.0.1-170-rel,sdata=False,bucket_topology=default:1>2;bucket0:1><2,upgrade_nodes=src,post-upgrade-actions=src-rebalanceout;dest-rebalanceout;dest-create_index


[Jenkins]
http://qa.hq.northscale.net/view/3.0%20By%20COMPONENT/job/centos_x64--01_03--XDCR_upgrade-P1/57/consoleFull


 Comments   
Comment by Sangharsh Agarwal [ 20/Oct/14 ]
All Offline upgrades from : 2.1.1-766-rel, 2.2.0-837-rel, 2.5.0-1059-rel, 2.5.1-1083-rel are failed with same issue.
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
Fixed be: http://review.couchbase.org/42299




[MB-12381] Memcached error #1 'Not found': Not found for vbucket Created: 20/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Sangharsh Agarwal Assignee: Sangharsh Agarwal
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Build 3.0.1-1422

Triage: Untriaged
Operating System: Centos 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump: [Source]
10.1.3.93 : https://s3.amazonaws.com/bugdb/jira/MB-12381/964b1150/10.1.3.93-10182014-317-diag.zip
10.1.3.93 : https://s3.amazonaws.com/bugdb/jira/MB-12381/db68adac/10.1.3.93-diag.txt.gz
10.1.3.94 : https://s3.amazonaws.com/bugdb/jira/MB-12381/3cd88c1e/10.1.3.94-diag.txt.gz
10.1.3.94 : https://s3.amazonaws.com/bugdb/jira/MB-12381/fdf72095/10.1.3.94-10182014-321-diag.zip
10.1.3.95 : https://s3.amazonaws.com/bugdb/jira/MB-12381/547b84ae/10.1.3.95-diag.txt.gz
10.1.3.95 : https://s3.amazonaws.com/bugdb/jira/MB-12381/f41c4d6b/10.1.3.95-10182014-325-diag.zip

[Destination]
10.1.3.96 : https://s3.amazonaws.com/bugdb/jira/MB-12381/72200414/10.1.3.96-diag.txt.gz
10.1.3.96 : https://s3.amazonaws.com/bugdb/jira/MB-12381/b04de4c6/10.1.3.96-10182014-329-diag.zip
10.1.3.97 : https://s3.amazonaws.com/bugdb/jira/MB-12381/d280d046/10.1.3.97-diag.txt.gz
10.1.3.97 : https://s3.amazonaws.com/bugdb/jira/MB-12381/fb1b989e/10.1.3.97-10182014-333-diag.zip
10.1.3.99 : https://s3.amazonaws.com/bugdb/jira/MB-12381/daa3faca/10.1.3.99-10182014-342-diag.zip
10.1.3.99 : https://s3.amazonaws.com/bugdb/jira/MB-12381/ed19b721/10.1.3.99-diag.txt.gz
10.1.2.12 : https://s3.amazonaws.com/bugdb/jira/MB-12381/1d65e66c/10.1.2.12-10182014-338-diag.zip
10.1.2.12 : https://s3.amazonaws.com/bugdb/jira/MB-12381/c56b0cc3/10.1.2.12-diag.txt.gz
Is this a Regression?: Yes

 Description   
[Test Error]
[2014-10-18 03:16:24,101] - [task:640] ERROR - Memcached error #1 'Not found': Not found for vbucket :912 to mc 10.1.3.95:11210, key: loadOne15901 delete operation.


[Test Steps]
1. Setup -> Source : 3Nodes, Destination: 4 Nodes.
2. Buckets-> default, sasl_bucket_1
3. XDCR -> Mode: Xmem, Bi-directional.
4. Load 20 Items on each node on Source (keys: loadOne*) and Destination (loadTwo*) on each bucket.
5. Disable compaction on "default" bucket.

[2014-10-18 03:14:44,352] - [rest_client:1940] INFO - 'default' bucket's settings will be changed with parameters: autoCompactionDefined=true&parallelDBAndViewCompaction=false&ramQuotaMB=1053


5. Update/Delete items on Source cluster and Create deleted items. -> Received MemcachedError on Source during Delete Operation itself.


[2014-10-18 03:16:24,101] - [task:640] ERROR - Memcached error #1 'Not found': Not found for vbucket :912 to mc 10.1.3.95:11210, key: loadOne15901 delete operation.

[2014-10-18 03:16:31,062] - [task:640] ERROR - Memcached error #1 'Not found': Not found for vbucket :144 to mc 10.1.3.93:11210, key: loadOne15227 delete operation.


[Notes]
- Test is passed with XDCR + SSL. Though It is not sure if it is related to XDCR directly.

 Comments   
Comment by Sangharsh Agarwal [ 20/Oct/14 ]
Ran this test separately, issue not reproduced.




[MB-12380] 27% regression in 80th percentile query latency with 1 bucket, 20M docs and stale=false parameter Created: 19/Oct/14  Updated: 25/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Test description:
80th percentile query latency (ms), 1 bucket x 20M x 2KB, non-DGM, 4 x 1 views, 500 mutations/sec/node, 400 queries/sec, stale=false

Observation:
80th percentile latency increase from 5457 ms to 6954 ms

links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_686_access
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_6c5_access

logs:
http://ci.sc.couchbase.com/job/zeus-64/1222/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1222/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1222/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1222/artifact/172.23.96.28.zip
http://ci.sc.couchbase.com/job/zeus-64/1222/artifact/web_log_172.23.96.25.json




[MB-12379] Default and Maximum lock time described incorrectly in Developer Guide Created: 19/Oct/14  Updated: 20/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 2.5.1, 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Chris Malarky Assignee: Amy Kurtzman
Resolution: Unresolved Votes: 0
Labels: documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to NCBC-691 Maximum and Default Locking times are... Open
relates to RCBC-186 Description of locking potentially mi... Open
relates to PYCBC-260 Default and Maximum lock described in... Resolved
relates to JCBC-596 Default and Maximum Lock Time needs c... New
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
The maximum lock in 2.5.1 and 3.0.0 is 30 secs, the default is 15 seconds. Any attempt to set a lock higher than the maximum results in the default being used. The Developer Guide needs updating to match this behaviour.




[MB-12378] [ui] inclusive_end is off by default (was: Change in behaviour between 2.5 and 3.0 for inclusive_end default) Created: 18/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: UI
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Minor
Reporter: marcusr Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: Unknown

 Description   
When using the web console to run queries against views, on 2.5 the default query string is:

?stale=false&connection_timeout=60000&limit=10&skip=0

even when not set to true in the filter results dialog.

On version 3.0 inclusive_end is set to false

?stale=false&inclusive_end=false&connection_timeout=60000&limit=10&skip=0

which can catch you out if you are running a query that returns a single document. This is not necessarily a regression but is a change which caught me out.



 Comments   
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
it's back to defaulting to true now. Will be part of 3.0.1

Fixed by this commit: http://review.couchbase.org/#/c/42301/




[MB-12377] SAMPLE clause with N1QL for queries to target only smaller subset of data for a quicker but inprecise answer to query Created: 18/Oct/14  Updated: 18/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: cbq-DP3
Fix Version/s: sherlock
Security Level: Public

Type: Improvement Priority: Major
Reporter: Cihan Biyikoglu Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
SAMPLE clause can be useful to limit the index or bucket scan we need to do to answer a query. we could also specify a special flag to only query data already resident in memory.




[MB-12376] Should add http_access.log to the list of log files in documentation Created: 17/Oct/14  Updated: 24/Oct/14  Resolved: 24/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Don Pinto Assignee: Ruth Harris
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
The admin access log feature records server requests (including admin logins) coming through the REST or Couchbase admin console.

See MB-10020

 Comments   
Comment by Don Pinto [ 24/Oct/14 ]
Ruth, can you please look at this issue ?

Thanks,
Comment by Ruth Harris [ 24/Oct/14 ]
Fixed.

Note: changes are published within a day




[MB-12375] 315% regression in 80th percentile query latency with 1 Bucket, 20M docs, non-DGM scenario with 4x1 views Created: 17/Oct/14  Updated: 25/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Test description:
80th percentile query latency (ms), 1 bucket x 20M x 2KB, non-DGM, 4 x 1 views, 500 mutations/sec/node, 400 queries/sec

Observation:
80th percentile latency increased from 13ms to 54ms

links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_2c1_access
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_eba_access

logs:
http://ci.sc.couchbase.com/job/zeus-64/1221/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1221/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1221/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1221/artifact/172.23.96.28.zip
http://ci.sc.couchbase.com/job/zeus-64/1221/artifact/web_log_172.23.96.25.json


 Comments   
Comment by Volker Mische [ 20/Oct/14 ]
I've added the label "Windows" as it really makes a difference. As the performance looks right on Linux.
Comment by Volker Mische [ 20/Oct/14 ]
Removed the "windows" label again as I just found out that there's also a way to set the "Operating System".




[MB-12374] 115% regression in 80th percentile query latency with 1 bucket, 100M documents and 4x1 views. Created: 17/Oct/14  Updated: 25/Oct/14

Status: Open
Project: Couchbase Server
Component/s: view-engine
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Test description:
80th percentile query latency (ms), 1 bucket x 100M x 2KB, DGM, 4 x 1 views, 500 mutations/sec/node, 400 queries/sec

Observation:
80th percentile latency increased from 13ms to 28ms.

links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_df0_access
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_c2e_access

logs:
http://ci.sc.couchbase.com/job/zeus-64/1223/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1223/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1223/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1223/artifact/172.23.96.28.zip
http://ci.sc.couchbase.com/job/zeus-64/1223/artifact/web_log_172.23.96.25.json



 Comments   
Comment by Volker Mische [ 20/Oct/14 ]
I've added the label "Windows" as it really makes a difference. As the performance looks right on Linux.
Comment by Volker Mische [ 20/Oct/14 ]
Removed the "windows" label again as I just found out that there's also a way to set the "Operating System"




[MB-12373] Tracking Item: Sync GW moving to DCP Created: 17/Oct/14  Updated: 17/Oct/14

Status: Open
Project: Couchbase Server
Component/s: DCP
Affects Version/s: 3.0
Fix Version/s: sherlock
Security Level: Public

Type: Improvement Priority: Major
Reporter: Cihan Biyikoglu Assignee: Adam Fraser
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
tracking the work in syncGW - https://github.com/couchbase/sync_gateway/issues/409

 Comments   
Comment by Cihan Biyikoglu [ 17/Oct/14 ]
created for tracking the item on syncGW and any asks that may come back.




[MB-12372] Fix the typo on the first Title Created: 17/Oct/14  Updated: 17/Oct/14  Resolved: 17/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Anil Kumar Assignee: Ruth Harris
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
http://docs.couchbase.com/developer/dev-guide-3.0/cb-vs-rdbms.html - "Comparing Couchbase and traditional RDMS"

Fix RDMS => RDBMS

 Comments   
Comment by Ruth Harris [ 17/Oct/14 ]
Fixed and pushed to Github.




[MB-12371] Incremental CBBackup shouldn't consume additional space with no delta Created: 17/Oct/14  Updated: 17/Oct/14  Resolved: 17/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: tools
Affects Version/s: 3.0, 3.0-Beta
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Anil Kumar Assignee: Bin Cui
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Debian 6
CentOS 6.5
Couchbase Server 3.0.0

Issue Links:
Relates to
Triage: Triaged
Is this a Regression?: Unknown

 Description   
Customer is reporting that cbbackup unexpectedly consumes additional storage in the following scenario:

1. Ensure that no operations can be performed against the Couchbase Server cluster
2. Perform a full backup of all buckets/nodes with `-m full`
3. Note disk usage of backup target directory
4. Perform a cumulative backup of all buckets/nodes with `-m accu`
5. Note disk usage of backup target has increased approximately 50%

I was able to setup a basic test on a cluster doing no work after an initial cbworkloadgen of 50k items and observed the same behavior as can be seen here:

[root@brian4 opt]# du -sh couchbase_backups/
4.0K couchbase_backups/

[root@brian4 opt]# /opt/couchbase/bin/cbbackup http://brian4.local:8091 /opt/couchbase_backups/ -m full -u Administrator -p couchbase
  [####################] 100.0% (50000/estimated 50000 msgs)
bucket: makura, msgs transferred...
       : total | last | per sec
 byte : 15773320 | 15773320 | 805225.6
done

[root@brian4 opt]# du -sh couchbase_backups/
26M couchbase_backups/

[root@brian4 opt]# /opt/couchbase/bin/cbbackup http://brian4.local:8091 /opt/couchbase_backups/ -m accu -u Administrator -p couchbase
  [############# ] 66.4% (33224/estimated 50000 msgs)
bucket: makura, msgs transferred...
       : total | last | per sec
 byte : 10485649 | 10485649 | 703111.0
done

[root@brian4 opt]# du -sh couchbase_backups/
42M couchbase_backups/

Why is there additional storage being consumed if nothing has changed on the cluster between backup invocations?

Thanks!


 Comments   
Comment by Bin Cui [ 17/Oct/14 ]
http://review.couchbase.org/#/c/42225/




[MB-12370] No reloc.sh in opt/couchbase/bin/install/reloc.sh Created: 17/Oct/14  Updated: 17/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Juan Luis Pérez Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: No

 Description   
I downloaded the couchbase from the downloads page. Couchbase 3.0.0 for ubuntu 64bits and there isn't the reloc.sh file to install as non-root




[MB-12367] cbq-engine crashes after first query run after building cbq-engine Created: 16/Oct/14  Updated: 16/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Iryna Mironava Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
last commit: 4eb2b16415cfd771190a9bbca3a211a31220a603
1) build cbq-engine
2) run cbq-engine

it crashes:
_time="2014-10-16T09:34:38-07:00" _level="INFO" _msg="New site created with url http://10.1.3.176:8091"
_time="2014-10-16T09:34:38-07:00" _level="INFO" _msg="cbq-engine started" version="0.7.0" datastore="http://10.1.3.176:8091"
_time="2014-10-16T09:35:39-07:00" _level="INFO" _msg="Refreshing pool default"
2014/10/16 09:35:50 http: multiple response.WriteHeader calls
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x20 pc=0x5dff9c]

goroutine 17 [running]:
net/http.(*switchWriter).Write(0xc20018ec60, 0xc20066b000, 0xc, 0x800, 0x3300000000, ...)
/usr/local/go/src/pkg/net/http/chunked.go:0 +0x5c
bufio.(*Writer).Flush(0xc200197640, 0xc2001be7e0, 0x2ac0d239cc98)
/usr/local/go/src/pkg/bufio/bufio.go:465 +0xb9
net/http.(*response).Flush(0xc2001be7e0)
/usr/local/go/src/pkg/net/http/server.go:952 +0x4a
github.com/couchbaselabs/query/server/http.(*httpRequest).Flush(0xc2001ca0f0)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_response.go:241 +0x67
github.com/couchbaselabs/query/server/http.(*httpRequest).writeString(0xc2001ca0f0, 0xc2006d6530, 0xc, 0xa)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_response.go:135 +0x8d
github.com/couchbaselabs/query/server/http.(*httpRequest).Fail(0xc2001ca0f0, 0xc200631640, 0xc2006da550)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_response.go:33 +0xd2
github.com/couchbaselabs/query/server.(*Server).serviceRequest(0xc2001f7460, 0xc200174e60, 0xc2001ca0f0)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:107 +0x24d
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:93 +0x9a
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 1 [IO wait]:
net.runtime_pollWait(0x2ac0d238ddc0, 0x72, 0x0)
/usr/local/go/src/pkg/runtime/znetpoll_linux_amd64.c:118 +0x82
net.(*pollDesc).WaitRead(0xc2001bf980, 0xb, 0xc2001c1990)
/usr/local/go/src/pkg/net/fd_poll_runtime.go:75 +0x31
net.(*netFD).accept(0xc2001bf900, 0xb0da38, 0x0, 0xc2001c1990, 0xb, ...)
/usr/local/go/src/pkg/net/fd_unix.go:385 +0x2c1
net.(*TCPListener).AcceptTCP(0xc20022b1a8, 0x5d1f46, 0x2ac0d0e7ac90, 0x5d1f46)
/usr/local/go/src/pkg/net/tcpsock_posix.go:229 +0x45
net.(*TCPListener).Accept(0xc20022b1a8, 0xc2001a81e0, 0xc200665f98, 0xc2001bfd80, 0x0, ...)
/usr/local/go/src/pkg/net/tcpsock_posix.go:239 +0x25
net/http.(*Server).Serve(0xc2001a8bb0, 0xc2001ff700, 0xc20022b1a8, 0x0, 0x0, ...)
/usr/local/go/src/pkg/net/http/server.go:1542 +0x85
net/http.(*Server).ListenAndServe(0xc2001a8bb0, 0xc2001ecb40, 0xc2001a8ba0)
/usr/local/go/src/pkg/net/http/server.go:1532 +0x9e
github.com/couchbaselabs/query/server/http.(*HttpEndpoint).ListenAndServe(0xc2001a8ba0, 0x1, 0xa0d820)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_endpoint.go:36 +0x2a
main.main()
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/main/main.go:96 +0x739

goroutine 2 [syscall]:

goroutine 4 [IO wait]:
net.runtime_pollWait(0x2ac0d238df00, 0x72, 0x0)
/usr/local/go/src/pkg/runtime/znetpoll_linux_amd64.c:118 +0x82
net.(*pollDesc).WaitRead(0xc2001bf080, 0xb, 0xc2001c1990)
/usr/local/go/src/pkg/net/fd_poll_runtime.go:75 +0x31
net.(*netFD).accept(0xc2001bf000, 0xb0da58, 0x0, 0xc2001c1990, 0xb, ...)
/usr/local/go/src/pkg/net/fd_unix.go:385 +0x2c1
net.(*UnixListener).AcceptUnix(0xc200196700, 0x0, 0xc2001a5898, 0x77c32a)
/usr/local/go/src/pkg/net/unixsock_posix.go:286 +0x49
net.(*UnixListener).Accept(0xc200196700, 0x0, 0x0, 0x0, 0x0, ...)
/usr/local/go/src/pkg/net/unixsock_posix.go:297 +0x49
github.com/couchbaselabs/retriever/logger.doHandleConnections(0xc2001bd780, 0xa3d810, 0xa)
/root/tuq/gocode/src/github.com/couchbaselabs/retriever/logger/accept.go:50 +0x32f
github.com/couchbaselabs/retriever/logger.handleConnections(0xc2001bd780, 0xa3d810, 0xa)
/root/tuq/gocode/src/github.com/couchbaselabs/retriever/logger/accept.go:24 +0x39
created by github.com/couchbaselabs/retriever/logger.NewLogger
/root/tuq/gocode/src/github.com/couchbaselabs/retriever/logger/logger.go:136 +0x26f

goroutine 279 [semacquire]:
sync.runtime_Semacquire(0xc2006b6020)
/usr/local/go/src/pkg/runtime/zsema_linux_amd64.c:165 +0x2e
sync.(*Cond).Wait(0xc2001bd9f0)
/usr/local/go/src/pkg/sync/cond.go:74 +0x95
io.(*pipe).read(0xc2001bd9c0, 0xc200669000, 0x1000, 0x1000, 0x0, ...)
/usr/local/go/src/pkg/io/pipe.go:52 +0x1f2
io.(*PipeReader).Read(0xc2006b6008, 0xc200669000, 0x1000, 0x1000, 0xc4, ...)
/usr/local/go/src/pkg/io/pipe.go:130 +0x5d
net/http.(*liveSwitchReader).Read(0xc2001bfda8, 0xc200669000, 0x1000, 0x1000, 0xc4, ...)
/usr/local/go/src/pkg/net/http/server.go:205 +0x91
io.(*LimitedReader).Read(0xc200668e20, 0xc200669000, 0x1000, 0x1000, 0xc4, ...)
/usr/local/go/src/pkg/io/io.go:394 +0xc0
net/http.(*switchReader).Read(0xc20018eb90, 0xc200669000, 0x1000, 0x1000, 0x0, ...)
/usr/local/go/src/pkg/net/http/chunked.go:0 +0x62
bufio.(*Reader).fill(0xc2001a8cc0)
/usr/local/go/src/pkg/bufio/bufio.go:79 +0x10c
bufio.(*Reader).ReadSlice(0xc2001a8cc0, 0x40be0a, 0x0, 0x0, 0x0, ...)
/usr/local/go/src/pkg/bufio/bufio.go:262 +0x202
bufio.(*Reader).ReadLine(0xc2001a8cc0, 0x0, 0x0, 0x0, 0x2ac0d0e86c00, ...)
/usr/local/go/src/pkg/bufio/bufio.go:293 +0x61
net/textproto.(*Reader).readLineSlice(0xc2001ecc30, 0xe005c872b, 0x42016f, 0xc2006475b0, 0x9b27a0, ...)
/usr/local/go/src/pkg/net/textproto/reader.go:55 +0x51
net/textproto.(*Reader).ReadLine(0xc2001ecc30, 0xc2006475b0, 0x1000, 0x5, 0x0, ...)
/usr/local/go/src/pkg/net/textproto/reader.go:36 +0x25
net/http.ReadRequest(0xc2001a8cc0, 0xc2006475b0, 0x0, 0x0)
/usr/local/go/src/pkg/net/http/request.go:510 +0x86
net/http.(*conn).readRequest(0xc2001bfd80, 0x0, 0x0, 0x0)
/usr/local/go/src/pkg/net/http/server.go:547 +0x1bc
net/http.(*conn).serve(0xc2001bfd80)
/usr/local/go/src/pkg/net/http/server.go:1052 +0x398
created by net/http.(*Server).Serve
/usr/local/go/src/pkg/net/http/server.go:1564 +0x266

goroutine 14 [chan receive]:
github.com/couchbaselabs/query/datastore/couchbase.keepPoolFresh(0xc2001a7b00)
/root/tuq/gocode/src/github.com/couchbaselabs/query/datastore/couchbase/couchbase.go:226 +0x5f
created by github.com/couchbaselabs/query/datastore/couchbase.loadNamespace
/root/tuq/gocode/src/github.com/couchbaselabs/query/datastore/couchbase/couchbase.go:131 +0x5de

goroutine 281 [chan receive]:
github.com/couchbaselabs/query/server/http.func·001()
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_request.go:93 +0x43
created by github.com/couchbaselabs/query/server/http.newHttpRequest
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/http/http_request.go:95 +0x6e8

goroutine 18 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 19 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 20 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 21 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 22 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 23 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 24 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 25 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 26 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 27 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 28 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 29 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 30 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 31 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 32 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 33 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 34 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 35 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 36 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 37 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 38 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 39 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 40 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 41 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 42 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 43 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 44 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 45 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 46 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 47 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 48 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 49 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 50 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 51 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 52 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 53 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 54 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 55 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 56 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 57 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 58 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 59 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 60 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 61 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 62 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 63 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 64 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 65 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 66 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 67 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 68 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 69 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 70 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 71 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 72 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 73 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 74 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 75 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 76 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 77 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 78 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 79 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 80 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 81 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 82 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 83 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 84 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 85 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 86 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 87 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 88 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 89 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 90 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 91 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 92 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 93 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 94 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 95 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 96 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 97 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 98 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 99 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 100 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 101 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 102 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 103 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 104 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 105 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 106 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 107 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 108 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 109 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 110 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 111 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 112 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 113 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 114 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 115 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 116 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 117 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 118 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 119 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 120 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 121 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 122 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 123 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 124 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 125 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 126 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 127 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 128 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 129 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 130 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 131 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 132 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 133 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 134 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 135 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 136 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 137 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 138 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 139 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 140 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 141 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 142 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 143 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 144 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 145 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 146 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 147 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 148 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 149 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 150 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 151 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 152 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 153 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 154 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 155 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 156 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 157 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 158 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 159 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 160 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 161 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 162 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 163 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 164 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 165 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 166 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 167 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 168 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 169 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 170 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 171 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 172 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 173 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 174 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 175 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 176 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 177 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 178 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 179 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 180 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 181 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 182 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 183 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 184 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 185 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 186 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 187 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 188 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 189 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 190 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 191 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 192 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 193 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 194 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 195 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 196 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 197 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 198 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 199 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 200 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 201 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 202 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 203 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 204 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 205 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 206 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 207 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 208 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 209 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 210 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 211 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 212 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 213 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 214 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 215 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 216 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 217 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 218 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 219 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 220 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 221 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 222 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 223 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 224 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 225 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 226 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 227 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 228 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 229 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 230 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 231 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 232 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 233 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 234 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 235 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 236 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 237 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 238 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 239 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 240 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 241 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 242 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 243 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 244 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 245 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 246 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 247 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 248 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 249 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 250 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 251 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 252 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 253 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 254 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 255 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 256 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 257 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 258 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 259 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 260 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 261 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 262 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 263 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 264 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 265 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 266 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 267 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 268 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 269 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 270 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 271 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 272 [chan receive]:
github.com/couchbaselabs/query/server.(*Server).doServe(0xc2001f7460)
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:92 +0x3c
created by github.com/couchbaselabs/query/server.func·002
/root/tuq/gocode/src/github.com/couchbaselabs/query/server/server.go:86 +0x58

goroutine 280 [runnable]:
net.runtime_pollWait(0x2ac0d238de60, 0x72, 0x0)
/usr/local/go/src/pkg/runtime/znetpoll_linux_amd64.c:118 +0x82
net.(*pollDesc).WaitRead(0xc2001bfd70, 0xb, 0xc2001c1990)
/usr/local/go/src/pkg/net/fd_poll_runtime.go:75 +0x31
net.(*netFD).Read(0xc2001bfcf0, 0xc2006b8000, 0x8000, 0x8000, 0x0, ...)
/usr/local/go/src/pkg/net/fd_unix.go:195 +0x2b3
net.(*conn).Read(0xc200665f98, 0xc2006b8000, 0x8000, 0x8000, 0x8000, ...)
/usr/local/go/src/pkg/net/net.go:123 +0xc3
io.Copy(0xc2006b7000, 0xc2006b6010, 0xc2001c1b10, 0xc200665f98, 0x0, ...)
/usr/local/go/src/pkg/io/io.go:348 +0x1c6
net/http.func·004()
/usr/local/go/src/pkg/net/http/server.go:162 +0x66
created by net/http.(*conn).closeNotify
/usr/local/go/src/pkg/net/http/server.go:168 +0x1c6




[MB-12366] unable to build cbq-engine (undefined: couchbase.PoolServices) Created: 16/Oct/14  Updated: 22/Oct/14

Status: Reopened
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: cbq-DP4
Security Level: Public

Type: Bug Priority: Test Blocker
Reporter: Iryna Mironava Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
[root@grape-001 query]# ./build.sh
cd parser/n1ql
nex...
goyacc...
go build...
cd server/main
go build -o cbq-engine...
# github.com/couchbaselabs/query/clustering/couchbase
../../clustering/couchbase/clustering_cb.go:93: undefined: couchbase.PoolServices
../../clustering/couchbase/clustering_cb.go:94: c.cbConn.GetPoolServices undefined (type *couchbase.Client has no field or method GetPoolServices)
cd shell
go build -o cbq...
cd tutorial
go build


 Comments   
Comment by Gerald Sangudi [ 16/Oct/14 ]
Fixed. Please do:

git pull
build.sh

Thanks.
Comment by Iryna Mironava [ 22/Oct/14 ]
I see it again
[root@grape-001 query]# ./build.sh
go get
cd parser/n1ql
nex...
goyacc...
go build...
cd server/main
go build -o cbq-engine...
# github.com/couchbaselabs/query/clustering/couchbase
../../clustering/couchbase/clustering_cb.go:93: undefined: couchbase.PoolServices
../../clustering/couchbase/clustering_cb.go:94: c.cbConn.GetPoolServices undefined (type *couchbase.Client has no field or method GetPoolServices)
cd shell
go build -o cbq...
cd tutorial
go build
[root@grape-001 query]#


last commits are:
[root@grape-001 query]# git log
commit b9b9bcc250ed08bedfe2098554c5882121e24709
Author: geraldss <gerald@couchbase.com>
Date: Tue Oct 21 16:23:14 2014 -0700

    Apply golang fmt.

commit 6b05c6c506d9c375dcfd7ad82e3c04b6aa85423e
Author: geraldss <gerald@couchbase.com>
Date: Sun Oct 19 18:17:05 2014 -0700

    Change INSERT and UPSERT syntax to allow keys to exist outside of values.





[MB-12365] ep_testsuite.cc:6288 Test failed: `Expected reading the value back in to update the read counter' Created: 16/Oct/14  Updated: 21/Oct/14  Resolved: 21/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: sherlock
Fix Version/s: sherlock
Security Level: Public

Type: Bug Priority: Major
Reporter: Dave Rigby Assignee: Mike Wiederhold
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: MacOSX 64-bit
Is this a Regression?: Unknown

 Description   
Running the ep_testsuite from top-of-trunk (ep_engine: GIT:2473b19) I see the following error *after* reverting the recent-ish change to add memory hooks to mock_server[1]:

Running [0078/0293]: io stats (couchstore).../Users/dave/repos/couchbase/server/source/ep-engine/tests/ep_testsuite.cc:6288 Test failed: `Expected reading the value back in to update the read counter' (get_int_stat(h, h1, "ro_0:io_num_read", "kvstore") == 1 && get_int_stat(h, h1, "ro_0:io_read_bytes", "kvstore") == 4)

To reproduce:

1. Apply http://review.couchbase.org/#/c/41647/ (to fix the mem_used errors).
2. cd build/ep-engine && make test

(or specific failing test: ./engine_testapp -E ep.so -T ep_testsuite.so -e "flushall_enabled=true;ht_size=13;ht_locks=7")

As an aside, do we not have a CI build testing this?

[1]: http://review.couchbase.org/#/c/41647/

 Comments   
Comment by Chiyoung Seo [ 16/Oct/14 ]
Mike,

Seems like a regression from the code refactoring and backfill changes in CouchKVStore
Comment by Mike Wiederhold [ 16/Oct/14 ]
I just want to note that doesn't appear be a regression. From what it sounds like Dave is saying when I make a certain change which does not exist in the master branch this test fails. I'll take a look at it, but I have not seen this test case fail anywhere.
Comment by Mike Wiederhold [ 16/Oct/14 ]
Dave,

It appears that one of the merges into the master branch was done incorrectly and now master requires a c++ 11 compiler. As a result I can not currently build the master branch on any of the machines I use.
Comment by Dave Rigby [ 16/Oct/14 ]
@MIke: No idea about that - all I found is that my change (3 weeks ago! to memcached) - caused some ep_engine tests to fail. Even if I back out that change - see http://review.couchbase.org/#/c/41647/ - ep_engine still fails (as per this MB).

It baffles me that ep_engine's unit tests have been broken for (at least) 3 weeks and no-one has noticed. Surely we should have a CI build in place to check for such things...

On the topic of C++11, all I know is that Trond has starting using C++11 features in memcached.
 
Comment by Dave Rigby [ 16/Oct/14 ]
(additionally - if it's any help I can build master on OS X (Mavericks) and Ubuntu 14.04 no problem).
Comment by Mike Wiederhold [ 16/Oct/14 ]
I think my memcached master branch wasn't being checked out properly when ran my tests so I was still using the 3.0.1 branch. I can see in the timings.cc file there are reference to c11 atomics that Trond removed in the 3.0.1 branch, but it appears those changes are not in the master branch. I'll see if I can fix it right now.
Comment by Mike Wiederhold [ 16/Oct/14 ]
Please see the memcached changes to fix the c++11 issues.

http://review.couchbase.org/#/c/42219/
http://review.couchbase.org/#/c/42224/
Comment by Mike Wiederhold [ 21/Oct/14 ]
Cannot reproduce this on the latest code in the branch-master.xml manifest.
Comment by Mike Wiederhold [ 21/Oct/14 ]
I ran this on the wrong branch. The fix is below.

http://review.couchbase.org/#/c/42334/




[MB-12364] Improve logging on auto_failover:reset_auto_failover_count Created: 16/Oct/14  Updated: 24/Oct/14  Resolved: 16/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.5.1, 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Improvement Priority: Minor
Reporter: Chris Malarky Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to

 Description   
Would be very useful to see the reset_auto_failover_count from auto_failover.erl in the same logs as node failover, so user_log() rather than log_debug() ?

 Comments   
Comment by Aleksey Kondratenko [ 16/Oct/14 ]
http://review.couchbase.org/42215




[MB-12363] [ElasticSearch] Remote cluster's IP (of ES endpoint) is mangled from localhost to wlan0's address Created: 16/Oct/14  Updated: 20/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Minor
Reporter: Egmont Koblinger Assignee: Marty Schoch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Ubuntu 14.10-beta, 64 bit, CB-community-3.0.0, ElasticSearch 1.3.0, transport 2.0.0

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: Unknown

 Description   
Under Couchbase Console's XDCR tab, I set up a cluster reference to "127.0.0.1:9091" (or "localhost:9091") where my ElasticSearch is running. Then I set up a proper replication (using version 1).

At this moment, the cluster reference's IP address or hostname gets rewritten to my development laptop's wlan0 IP address, e.g. "192.168.0.10:9091".

The problem with this is that, depending on which network (e.g. work vs. home) I open the laptop, I get different IP address. That is, a previously set cluster reference becomes unusable, I have to destroy and create it again every time.

Expected behavior: Whatever hostname or IP address I specify there should always remain the same, CB should not change it. If I say "localhost", it should stay "localhost".

 Comments   
Comment by Aleksey Kondratenko [ 16/Oct/14 ]
This "renaming" happens because node's name appears to be "192.168.0.10".

In order to confirm I'll need collectinfo(s) from your cluster.
Comment by Egmont Koblinger [ 17/Oct/14 ]
Which node are you referring to, CB or ES? Is there a way to get that node name?

I started CB configuration from scratch (because the collectinfo is damn large otherwise, and anyways contains the ES password which is really not nice). I wish I could attach the 1.5MB file but I keep getting "Cannot attach file collectinfo-2014-10-17T115716-ns_1@127.0.0.1.zip: Unable to communicate with JIRA"

On the opening setup screen of CB there's a field "Configure Server Hostname", I left the default 127.0.0.1 there. I created a new bucket without replication, set up XDCR cluster reference followed by an actual replication to an already existing ES index.
Comment by Aleksey Kondratenko [ 17/Oct/14 ]
Ah I think I misunderstood.

Here's what happens at couchbase server side:

* when you set up cluster reference it goes to specified endpoint and fetches remote cluster info

* It will then rewrite reference if remote cluster info does not have host with same name.

So apparently elasticsearch plugin that's servicing :9091 is sending out node cluster info in this way.
Comment by Aleksey Kondratenko [ 17/Oct/14 ]
Passing this to ES plugin maintainer.
Comment by Marty Schoch [ 17/Oct/14 ]
Elasticsearch allows you to control which network address is used to advertise itself. Our plugin honors this configuration.

The user should find the line in their config file:

#network.publish_host: 192.168.0.1

Uncomment it, and change the publish_host value to the address they want. In this case 127.0.0.1
Comment by Egmont Koblinger [ 18/Oct/14 ]
Thanks guys for your kind responses, indeed setting network.publist_host works.

That being said, I don't understand the rationale behind this method of advertising the IP address and forcing the client to overwrite it. This fails in my particular use case, and might fail in other cases too (e.g. complicated firewall rules, or a host with two interfaces and no IP forwarding that requires that all incoming packets come with the destination address belonging to the incoming interface).

If I specify an IP address on the client (CB) and the client is able to reach the server (ES) then that IP address is working, why overwrite it to something else which might not work in tricky setups?

Looks to me like a step that overcomplicates things for no reason. What am I missing here? :)
Comment by Marty Schoch [ 18/Oct/14 ]
There are really two separate questions.

1. Why does Elasticsearch advertise its own address in this way?
and
2. Why does Couchbase update the XDCR configuration based on the information returned by Elasticsearch?

I can only answer #1.

The Couchbase Elasticsearch plugin was designed to operate within the existing Elasticsearch framework. Part of that includes behaving like the other Elasticsearch components and even sharing their configuration when it makes sense. Now, Elasticsearch, like many other distributed networking services needs to advertise to other services how it can be reached, sometimes this information is broadcast, or recorded in one place for consumption by someone else. In these cases you cannot rely on the idea of "just reach me again on the same address you did to get here approach" because the information is flowing the other direction. In these cases Elasticsearch will first attempt to "guess" which address it should use. Sometimes it guesses wrong and does not choose the most appropriate address. That is why they have the publish.host setting to allow you to override it.

In the cases where a client does initiate an incoming request why doesn't Elasticsearch always respond with that address? First, sometimes that isn't what the administrator wants. And second, I think when binding to a wildcard address (0.0.0.0) it isn't easy to determine from which interface the request came. (My recollection is that you separately bind to each address it is easier) I would say though that if Elasticsearch had a way to do this easily I would offer it as an option.

Perhaps Aleksey may provide insight into #2.
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
ns_server is behaving the way it behaves because target cluster members may change over time. So it has to track all cluster members and rewrite cluster reference when previous reference points to node that's not part of cluster anymore.

In your case there's no way to be sure that 127.0.0.1 is same (and will remain same) as your wlan ip that's advertised by ES.
Comment by Egmont Koblinger [ 20/Oct/14 ]
Thanks again guys for your responses. I'm new to this world of databases/replicas/etc, apparently there's a lot for me to learn about the standard practices here.




[MB-12362] Pillowfight performance negatively affected by specifying larger item amounts Created: 10/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: performance
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Thomas Anderson
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Centos 64-bit
Is this a Regression?: Unknown

 Description   
I can notice a major difference in pillowfight performance when running with '-I' set to a larger value than the default.

At the default of 1k, I can reach over 2.5M ops/sec...taking the same command with 1M items, it stops around 2M.

I'm not sure how much the difference would be noticed at lower thread counts and slower networking, but I think it does point to some bottleneck or inefficiency that could help across the board.

Mark, I think you mentioned something about some improvements coming to reduce shared object contention and other things? Is this related to that?



 Comments   
Comment by Mark Nunberg [ 10/Oct/14 ]
First of all, you'd need to make sure that the performance comparisons come about once the populate phase for the workload has been completed with the larger item amounts. Naturally creating more items will require a longer populate phase (the speedup of the populate phase is going to come in the next version).

Additionally you have the added load on the server side of potentially fetching items from disk or slower main memory, rather than the CPU's cache.
Comment by Mark Nunberg [ 13/Oct/14 ]
I don't think this is related to anything in the pillowfight code itself. There might be something I can do in the way of documentation though, if you can help me confirm the exact characteristics
Comment by Perry Krug [ 13/Oct/14 ]
Thanks Mark, I appreciate your help.

I ran these two commands one after another and noticed the performance difference:
cbc-pillowfight -U couchbase://&lt;host&gt;/&lt;bucket> -I 1000 -t 128 -B 10000 -c -1 -r 5 -n
cbc-pillowfight -U couchbase://&lt;host&gt;/&lt;bucket> -I 100000 -t 128 -B 10000 -c -1 -r 5 -n

(notice the high thread count and high batch size, this was necessary to push enough load...around 1M ops/sec. Also notice the "-n" to avoid any populate phase slowness)

If you can help me understand the difference as being expected, that's wonderful. If there's some work you can do to make them more consistent, even better ;-)
Comment by Mark Nunberg [ 15/Oct/14 ]
Perry: I've moved this as an MB and in the performance section; since I've seen the same results as you have, and have no reason to suspect anything in the client causing this
Thomas: I made the assumption you're the current assignee for "Performance" (Auto gave me Pavel..). Please reassign if this isn't correct




[MB-12361] Backport to 2.5.1 - implement access.log like functionality of port 8091 Created: 15/Oct/14  Updated: 21/Oct/14  Resolved: 15/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.2.0
Fix Version/s: 2.5.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Dave Finlay Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged

 Description   
This ticket tracks the backporting of http://www.couchbase.com/issues/browse/MB-10020 to 2.5.1 as a hot fix.

 Comments   
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
merged a bunch of commits ending here: http://review.couchbase.org/42181
Comment by Chris Hillery [ 15/Oct/14 ]
Updated rel-2.5.1.xml manifest (and cleaned up some 2.5.1.1-related stuff) here: http://review.couchbase.org/#/c/42189/

Build 2.5.1-1102 underway.




[MB-12359] Remove support for SSL v3 in memcached SSL server sockets to mitigate against the POODLE attack Created: 15/Oct/14  Updated: 16/Oct/14  Resolved: 16/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: memcached
Affects Version/s: 2.5.1, 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Dave Finlay Assignee: Trond Norbye
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to MB-12358 Remove support for SSL v3 in ns_serve... Resolved
Triage: Untriaged
Flagged:
Release Note
Is this a Regression?: No

 Description   
Poodle attack described here: http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html

More user friendly description here: http://blog.cryptographyengineering.com/2014/10/attack-of-week-poodle.html

My thinking is we currently fix this for 3.0.1 and then create an MB to backport to 2.5.2 whenever that ships.

Suggested fix: remove SSL v3 support in the versions the server SSL socket supports.

 Comments   
Comment by Trond Norbye [ 16/Oct/14 ]
http://review.couchbase.org/#/c/42199/
Comment by Dave Rigby [ 16/Oct/14 ]
Flagging as release note - we should highlight high-profile security fixes such as this.
Comment by Trond Norbye [ 16/Oct/14 ]
Fixed in 3.0.1




[MB-12358] Remove support for SSL v3 in ns_server SSL server sockets to mitigate against the POODLE attack Created: 15/Oct/14  Updated: 16/Oct/14  Resolved: 16/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.5.1, 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Dave Finlay Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to MB-12359 Remove support for SSL v3 in memcache... Resolved
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Poodle attack described here: http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html

More user friendly description here: http://blog.cryptographyengineering.com/2014/10/attack-of-week-poodle.html

My thinking is we currently fix this for 3.0.1 and then create an MB to backport to 2.5.2 whenever that ships.

Suggested fix: remove SSL v3 support in the versions the server SSL socket supports.

 Comments   
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
http://review.couchbase.org/42188
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
Actually forgot to do same for downstream listener of ssl proxy.
Comment by Aleksey Kondratenko [ 16/Oct/14 ]
ssl proxy is covered by: http://review.couchbase.org/42209




[MB-12357] Custom error message from updater Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Volker Mische Assignee: Volker Mische
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Make it possible to have a custom error message from the updater.




[MB-12356] unusual high number of gets per sec (20k) opening "Documents" view Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: UI
Affects Version/s: 3.0.1
Fix Version/s: bug-backlog
Security Level: Public

Type: Bug Priority: Critical
Reporter: Matt Ingenthron Assignee: Aleksey Kondratenko
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Unknown

 Description   
Reported by a user here: https://forums.couchbase.com/t/what-is-causing-high-number-of-gets-per-sec-20k-opening-documents-view-3-0-1/1746

Every time I click on "Documents" to view documents in a Bucket, the page hangs for a little bit while it loads. If I switch over to the General Bucket Analysis graph, I see some 20k gets/sec. I am currently able to produce this behavior consistently. There are no Views for this bucket.

 Comments   
Comment by rdev5 [ 15/Oct/14 ]
Please see https://github.com/rdev5/cachewarmer/tree/master for instructions on how I was able to reproduce this on a new 3.0.0/1 cluster.
Comment by Matt Ingenthron [ 15/Oct/14 ]
Thanks so much for the sample rdev5! That's hugely helpful in finding/addressing the issue.
Comment by rdev5 [ 15/Oct/14 ]
Sure thing. Hope you guys are able to track it down. Let me know if you need anything else.
Comment by rdev5 [ 15/Oct/14 ]
Just an added observation - It appears that flushing the bucket purges it of this behavior. Running the test project again brings it back (even after items have been expired).
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
We have tracked it down.

It's interesting combination of our fundamental lack of support of range ops and the way how expirations work.

Specifically:

* every time you open Documents section of UI it makes "get me 10 docs with lexicographically smallest keys".

* our in-memory layer is unable to handle it directly. So couchbase actually has to go to specific .couch files. This is where problem number one exists: it's unable to see docs that are created but are not persisted yet.

* getting 10 smallest keys from specific per-vbucket .couch file is efficient. But getting list of 10 smallest keys across all 1024 vbuckets is far less efficient. It's quick if your by-id btree of db files fit in page cache, but once you get to larger data sizes expect it to be very slow

* after we've got 10 smallest keys from underlying .couch files we fetch their bodies from caching layer. This is where second issue kicks in.

* It happens because actual expirations are lazy in couchbase (same as upstream memcached in fact). When document gets expired it does not get deleted immediately. Instead, when you GET some key, caching layer checks if document is expired and if it is, then it'll delete it and return "missing" response. There is however periodic task that periodically scans all keys and deletes expired documents.

* so this causes problem for views (both for DCP-based views of 3.0.0 and .couch-file based views of 2.x). And it causes similar "problem" for documents ui.

* so when underlying Documents UI REST API implementation gets list of keys and does GETs, it will in your case discover that those docs are actually gone already. It will try larger window and larger until it finds 10 "live" docs.

* and that's what is causing slowness for you


In general, Documents UI works for development environments (albeit with issues mentioned above). But don't expect Documents UI to be work ok for serious production deployments. It's just not ready.

Also, as far as I know there are no plans to fix it. There are some internal discussions about primary index related to niql work. But I'm not aware of any plans at all w.r.t. expirations problem. So I have no idea when this 2 issues that you're dealing with will be fixed.


Comment by rdev5 [ 15/Oct/14 ]
Two quick questions:

So basically avoid using the Documents UI in production altogether since it could possibly impact server performance for clients in production?

Are older versions like 2.2 and 2.5 also affected by this?
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
>> So basically avoid using the Documents UI in production altogether since it could possibly impact server performance for clients in production?

Yes.

>> Are older versions like 2.2 and 2.5 also affected by this?

Yes. Even more than 3.0, because 3.0's implementation is more optimized.




[MB-12355] Inconsistent placement of Delete button on XDCR page Created: 15/Oct/14  Updated: 16/Oct/14  Resolved: 16/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: UI
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Trivial
Reporter: Egmont Koblinger Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: Unknown

 Description   
The web console's XDCR page looks like:

<one particular remote cluster> [Delete] [Edit]
<one particular ongoing replication> [Settings] [Delete]

I find the inconsistent placement of the Delete button quite confusing, I think it should be either the first button at both places, or the last button at both.

(In the mean time I'm wondering why Edit and Settings are different words, both buttons take you to a dialog where you can edit the settings – albeit they're different, one allows you to edit all the properties, the other one only allows to edit the advanced parameters. So this is just an FYI.)

 Comments   
Comment by Aleksey Kondratenko [ 16/Oct/14 ]
Thanks for feedback.




[MB-12354] Log timestamps lag behind after a laptop suspend Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Minor
Reporter: Egmont Koblinger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Laptop with Ubuntu 14.10-beta, 64-bit; CB 3.0 community edition

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: Unknown

 Description   
I use my laptop for developing to-be-production CB-based software. If I suspend and later wake it up, the timestamps in the log files (e.g. /opt/couchbase/var/lib/couchbase/logs/couchdb.log) will lag behind by the amount my laptop spent suspended.

E.g. if I suspend it for 10 hours overnight, records logged at 2014-10-15T09:00:00 will have the timestamp 2014-10-14T23:00:00 or so. This makes timestamps in the log files effectively useless.

Expected behavior: all the timestamps should reflect the actual time at that point, as correctly known by the operating system, and as returned by the time()/gettimeofday()/localtime()/strftime()/etc. kernel/glibc calls.

(BTW this bug also makes me wonder whether DST changes are handled correctly. I haven't tested that.)




[MB-12353] [Windows]32% regression from 2.5.1 in Rebalance out with views and query workload. Created: 15/Oct/14  Updated: 25/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server, view-engine
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Rebalance out time increased from 242.7 to 322.3 minutes from 2.5.1 to 3.0.1.

Test details:
Rebalance-out (min), 4 -> 3, 1 bucket x 100M x 2KB, 1 x 1 views, 10K ops/sec, 400 queries/sec

Observations (2.5.1 vs 3.0.1):

12x increase in bg_fetch latency from 250us to 3000us.
23x decrease in avg disk update time from max of 70us to 3us.
~4x increase in 90 percentile query latency from 13ms to 46ms.
cache miss rate ~2% in both runs.
active resident ratio 20-25% in both runs.

machine details:
RAID 10 HDD
24 vCPU, 64 GB
links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_606_rebalance
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_20f_rebalance

logs:
http://ci.sc.couchbase.com/job/zeus-64/1218/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1218/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1218/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1218/artifact/172.23.96.28.zip

 Comments   
Comment by Venu Uppalapati [ 16/Oct/14 ]
Assigning to view team for initial investigation since rebalance out for KV case has lesser regression of 12.5%.




[MB-12352] Remove unnesscary couchstore open/reads from backfill Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 3.0
Fix Version/s: sherlock
Security Level: Public

Type: Bug Priority: Major
Reporter: Jim Walker Assignee: Jim Walker
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Observed on many.

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Whilst investigating rebalance performance (time, disk and net I/O) I was curious as to why a 100% resident rebalance was reading from disk (Linux disk caches dropped prior to rebalance).

Found DCP backfill performs a call to retrieve the number of items in a couchstore data file followed by a "dump" of the file. These are two open/closes, the first one looks to be removable.

Given that the dump of seqno -> end is going to execute the CacheCallback for each K, we can use the CacheCallback to also increment "backfill-remaining"

This appears a safe thing todo, I can't see that the dump/scan requires the backfill count? If it does then we can scrap this simple fix and i'll move along to the next set of tests and investigations :)

With the patch it was hard to see if there's a perf improvement, but we do reduce the amount of data read from disk. The clearest stat was measuring how many pread64's a node performed during rebalance. Average of 2 runs shows the following.

1. current master - 28,902 calls to pread64
2. With patch - 24,170 calls to pread64

That's 16% less. It's gotta be useful?



 Comments   
Comment by Jim Walker [ 15/Oct/14 ]
http://review.couchbase.org/42156
Comment by Jim Walker [ 15/Oct/14 ]
When I say hard to measure perf improvement, this refers to real-time of the rebalance. The rebalance without this fix had a variation of around 20% and no obvious/dramatic difference after the patch, only directly measuring pread was any "benefit" observed.

With bigger and bigger vbuckets, this may be more useful. I only had 4.5 million items (vbucket disk size around 1.7MB)




[MB-12351] Faulty ISO 8601 timestamp format in log files (one-digit hour) Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Trivial
Reporter: Egmont Koblinger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 5m
Time Spent: Not Specified
Original Estimate: 5m
Environment: Ubuntu 14.04 and 14.10-beta, 64-bit; CB 3.0.0 community edition

Triage: Untriaged
Operating System: Ubuntu 64-bit
Is this a Regression?: Unknown

 Description   
The log files under /opt/couchbase/var/lib/couchbase/logs contain timestamps along the lines of
2014-10-15T9:59:50.272

Even though the ISO 8601 standard itself is not available for free so I can't verify that for sure, but extracts of that (such as http://en.wikipedia.org/wiki/ISO_8601 and http://www.w3.org/TR/NOTE-datetime) state that the hour should be HH, that is, two digits, zero-padded if necessary.





[MB-12350] DCP info message contains misleading statistics. Created: 15/Oct/14  Updated: 15/Oct/14

Status: Open
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 3.0
Fix Version/s: sherlock
Security Level: Public

Type: Bug Priority: Major
Reporter: Jim Walker Assignee: Jim Walker
Resolution: Unresolved Votes: 0
Labels: supportability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Observed on Linux Ubuntu 12/14. Small 2x node cluster with 100% resident data set.

Triage: Untriaged
Is this a Regression?: No

 Description   
I've been investigating rebalance of varying data-sets and spotted on a 100% resident data set the following message in memcached logs.

(vb 1022) Stream closing, 487 items sent from disk, 0 items sent from memory, 487 was last seqno sent

0 items from memory? 487 from disk! This was worrying, but investigations showed we were sending from memory, just the statistic gathering was incorrect.

A patch is ready which fixes this and I now have messages as follows, which are accurate.

(vb 1022) Stream closing, 0 items sent from disk, 487 items sent from memory, 487 was last seqno sent

 Comments   
Comment by Jim Walker [ 15/Oct/14 ]
http://review.couchbase.org/42153




[MB-12349] [Windows]65% regression from 2.5.1 in Rebalance after failover with views and query workload. Created: 15/Oct/14  Updated: 20/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Venu Uppalapati Assignee: Nimish Gupta
Resolution: Unresolved Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Windows 64-bit
Is this a Regression?: Yes

 Description   
Rebalance after failover time increased from 310.4 to 513 minutes from 2.5.1 to 3.0.1.

Test details:
Rebalance after failover (min), 3 -> 4, 1 bucket x 100M x 2KB, 1 x 1 views, 10K ops/sec, 400 queries/sec

Observations (2.5.1 vs 3.0.1):

15x increase in bg_fetch latency from 180us to 2750us.
23x decrease in avg disk update time from max of 70us to 3us.
4x increase in 90 percentile query latency from 14ms to 55ms.
cache miss rate under 2% in both runs.
active resident ratio ~30% in both runs.

machine details:
RAID 10 HDD
24 vCPU, 64 GB

links:
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_301-1330_749_rebalance
http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=zeus_251-1083_40b_rebalance

logs:
http://ci.sc.couchbase.com/job/zeus-64/1217/artifact/172.23.96.25.zip
http://ci.sc.couchbase.com/job/zeus-64/1217/artifact/172.23.96.26.zip
http://ci.sc.couchbase.com/job/zeus-64/1217/artifact/172.23.96.27.zip
http://ci.sc.couchbase.com/job/zeus-64/1217/artifact/172.23.96.28.zip
http://ci.sc.couchbase.com/job/zeus-64/1217/artifact/master_events.zip

 Comments   
Comment by Venu Uppalapati [ 15/Oct/14 ]
Assigning to view team for initial investigation since rebalance for KV case does not show regression.
Comment by Nimish Gupta [ 20/Oct/14 ]
Rebalance is taking more time in 3.0.1 compared to 2.5 and currently we are suspecting it is due to http://www.couchbase.com/issues/browse/MB-11589. Venu, could you please verify that this issue is seen on Linux also and please mention the test case also.
Comment by Venu Uppalapati [ 20/Oct/14 ]
Rebalance after failover with views/query on Linux has regressed much less compared to Windows. The rebalance time(linux) went up from 184.9 to 210.5 minutes(13.8 % regression). The test details are provided in the description section, are you looking for the perfrunner test implementation?




[MB-12348] Document the Type parameter for Creating XDCR replications Created: 14/Oct/14  Updated: 14/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 2.2.0, 2.5.1, 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Anil Kumar Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
http://docs.couchbase.com/couchbase-manual-2.5/cb-rest-api/#creating-xdcr-replications doesn't document the parameter "type" [values: xmem, capi].




[MB-12347] unable to startup couchbase server w/ builds 3.0.1-1393+ Created: 14/Oct/14  Updated: 16/Oct/14  Resolved: 16/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: installer
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Test Blocker
Reporter: Ketaki Gangal Assignee: Bin Cui
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Yes

 Description   
All qe-jobs fail post installation of 3.0.1-1392 fail with permission errors as below

http://qa.sc.couchbase.com/job/centos_x64--00_01--qe-sanity-P0/1093/console

2014-10-14 10:08:25,997 - root - ERROR - bash: /opt/couchbase/var/lib/couchbase/logs/start.log: Permission denied
2014-10-14 10:08:25,999 - root - INFO - Starting couchbase-server[FAILED]
2014-10-14 10:08:25,999 - root - ERROR - something wrong happened on 172.23.106.132!!! output:['Starting couchbase-server[FAILED]'], error:['bash: /opt/couchbase/var/lib/couchbase/logs/start.log: Permission denied'], track_words:('error', 'fail')
2014-10-14 10:08:25,999 - root - INFO - running command.raw on 172.23.106.132: rm -f *-diag.zip
2014-10-14 10:08:26,082 - root - INFO - command executed successfully
2014-10-14 10:08:26,083 - root - INFO - wait 5 seconds for membase server to start
2014-10-14 10:08:26,730 - root - INFO - command executed successfully
2014-10-14 10:08:26,731 - root - ERROR - warning: user $CB_USR does not exist - using root
2014-10-14 10:08:26,731 - root - ERROR - warning: group $CB_GRP does not exist - using root
2014-10-14 10:08:26,731 - root - ERROR - warning: user $CB_USR does not exist - using root
2014-10-14 10:08:26,731 - root - ERROR - warning: group $CB_GRP does not exist - using root
2014-10-14 10:08:26,732 - root - ERROR - warning: user $CB_USR does not exist - using root
2014-10-14 10:08:26,732 - root - ERROR - warning: group $CB_GRP does not exist - using root
2014-

Note : The exact same setup/ env works for any build prior to 1392.

No new changes on testrunner, should impact the user-permissions.

- How is CB_USR, CB_GROUP to be used during couchbase-installation?



 Comments   
Comment by Bin Cui [ 14/Oct/14 ]
http://review.couchbase.org/#/c/42138/
Comment by Aruna Piravi [ 15/Oct/14 ]
Don't see this fixed yet. Build - 3.0.1-1406-rel.
Comment by Ketaki Gangal [ 16/Oct/14 ]
broken likewise for build 301-1416 from oct 16
http://qa.sc.couchbase.com/job/centos_x64--00_01--qe-sanity-P0/1107/console
Comment by Ketaki Gangal [ 16/Oct/14 ]
Works as expected on 301-1417 build

http://qa.sc.couchbase.com/job/centos_x64--00_01--qe-sanity-P0/1108/




[MB-12346] unable to update json document Created: 14/Oct/14  Updated: 14/Oct/14

Status: Open
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Iryna Mironava Assignee: Gerald Sangudi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Centos 64-bit
Is this a Regression?: Unknown

 Description   
have document b1 ({'name':'abc'}) in bucket b0
query:
cbq> update b0 keys ['b1'] set name='aa';
{
    "signature": null,
    "results": [
    ],
    "errors": [
        {
            "caller": "couchbase:528",
            "cause": "json: cannot unmarshal object into Go value of type []string",
            "code": 5000,
            "key": "Internal Error",
            "message": "Failed to perform update"
        }
    ],
    "state": "errors",
    "metrics": {
        "elapsedTime": "3.004ms",
        "executionTime": "2.644ms",
        "resultCount": 0,
        "errorCount": 1
    }
}





[MB-12345] Version 3.0.0-1209-rel prompts for update which fails Created: 14/Oct/14  Updated: 14/Oct/14  Resolved: 14/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: build, installer
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: kouiti Assignee: Chris Hillery
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-10-14 at 10.11.02.png     PNG File Screen Shot 2014-10-14 at 10.11.16.png     PNG File Screen Shot 2014-10-14 at 10.13.20.png    
Issue Links:
Duplicate
duplicates MB-10214 Mac version update check is incorrect... Open
duplicates MB-7250 Mac OS X App should be signed by a va... Open
Triage: Untriaged
Operating System: MacOSX 64-bit
Is this a Regression?: Unknown

 Description   
As I have experienced a couple of days ago, I'm still having trouble to update.

So, today, I've completely uninstalled the previous CouchBase application from my MacOS X so I can start from scratch, then I downloaded the Couchbase 3 from: http://www.couchbase.com/download

But the file I got has a creation date as: Tuesday, September 9, 2014 at 18:59 (which is, as I think, before version 3 came out) and the version I get is: Version 3.0.0-1209-rel (the same as I had before)

This is why I thought maybe the link is broken, and what convinced me more, is when I started the app for the FIRST time it prompted me for an update which fails with the error message: The update is improperly signed.

 Comments   
Comment by Chris Hillery [ 14/Oct/14 ]
The download you are getting is correct; 3.0.0-1209 is the release version of 3.0.0. The date is before 3.0.0 came out due to the QA cycle required to verify the release.

So there are two problems here:

1. If you are already running 3.0.0-1209, it shouldn't prompt you to update. See MB-10214.

2. The download isn't properly signed, which is a long-known problem: MB-7250.

I'm marking this as a Duplicate. Further work on these issues will be tracked on the corresponding tickets.




[MB-12344] Clearly document instructions for compiling Couchbase from source code on multiple platforms. Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Aruna Piravi Assignee: Chiyoung Seo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Fresh compilation of Couchbase is time-consuming mainly because of incomplete instructions like

- Which version of gcc/cc/clang to use?
- What packages are needed? Any specific versions?

https://github.com/couchbase/tlm#macosx is almost right but it doesn't include gperftools and dependency on v8 version 3.18.5. I spent an entire day trying to compile couchbase until I stumbled upon this page.

Can we have this page updated? Also not many ppl know about this page. There's still copies of stale and incorrect instructions in many of our wiki pages (eg. - new hire page).

Let's have one correct set of instructions everywhere. It also makes sense for Dev to own it so it can be updated when 3rd party dependencies change.

I was not sure whom to reach. Please feel free to assign to anyone. Thanks.




[MB-12343] Docs updated with CLI/REST API instructions for setting cluster name Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on MB-12341 couchbase-cli needs to be able to set... Open

 Description   
Waiting on mb-12341 I believe, but we will want to fill out the documentation with CLI and REST API instructions for setting the cluster name (http://docs.couchbase.com/admin/admin/UI/ui-settings-cluster.html)




[MB-12342] Man page for couchbase-cli Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: tools
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: Bin Cui
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
It would be extremely helpful to have a man page for couchbase-cli. Really would be great for all cli tools, but this is the main one that our customers use for automated deployments.






[MB-12341] couchbase-cli needs to be able to set cluster name Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: tools
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Bin Cui
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks MB-12343 Docs updated with CLI/REST API instru... Open
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
With the new ability to set a cluster name, we need that ability extended to the couchbase-cli and then documented as such.




[MB-12340] Need to register event listener for connectors Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: cross-datacenter-replication
Affects Version/s: bug-backlog
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Minor
Reporter: Yu Sui Assignee: Yu Sui
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Now that connectors can also raise events, possibly error events, pipeline supervisor needs to register error listeners for connectors. This requires changes to pipeline manager as well.




[MB-12339] Make FDB_MAX_KEYLEN, FDB_MAX_METALEN public Created: 13/Oct/14  Updated: 14/Oct/14  Resolved: 14/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: forestdb
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Minor
Reporter: Jens Alfke Assignee: Chiyoung Seo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Since key length is quite limited (3840 bytes), it's entirely likely a client can hit the limit. So it would be useful for client code to know the limit so it can avoid it at runtime, for example if keys may be based on user-entered data. However, the value is currently defined only in the internal header option.h.

The same goes for metadata length; this is a lot larger (64k), but could still be exceeded by clients.

 Comments   
Comment by Chiyoung Seo [ 13/Oct/14 ]
The change is in gerrit for review:

http://review.couchbase.org/#/c/42086/
Comment by Chiyoung Seo [ 14/Oct/14 ]
Merged.




[MB-12338] stale=false is incorrectly formatted. Created: 13/Oct/14  Updated: 13/Oct/14  Resolved: 13/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Patrick Varley Assignee: Ruth Harris
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://docs.couchbase.com/admin/admin/rel-notes/rel-notes3.0.html

Attachments: PNG File Screen Shot 2014-10-13 at 22.37.11.png    
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
Under the "Views behavior change" in the release notes. The 2nd "stale=false" is incorrectly formatted.

Please see attached screenshot.


 Comments   
Comment by Ruth Harris [ 13/Oct/14 ]
Fixed.




[MB-12336] Installing our CentOS 6 RPM on a CentOS 5.x system succeeds but fails to start Created: 13/Oct/14  Updated: 13/Oct/14  Resolved: 13/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: installer
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Bin Cui
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates MB-9560 /etc/init.d/couchbase-server startup ... Open
Triage: Untriaged
Is this a Regression?: Unknown

 Description   
I realize it's a user-error, but I think it's common enough that we should try to mitigate the effect.

The CentOS 6 install succeeds and tries to start the server, but it then goes into an infinite restart loop that is quite hard to diagnose.




[MB-12335] [/diag/eval only] Disable bucket reload when configuration changes are made Created: 13/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to MB-10932 Disable force-respawn of memcached up... Resolved
Triage: Untriaged
Is this a Regression?: No

 Description   
Given the addition of the GIO and bucket priority in 3.0, I would like to ask that we disable ns_server's forced reload of the bucket when the following items are changed (and therefore allow them to be changed if they cannot currently):
-GIO thread count
-Bucket IO priority
-ejection policy

These are very frequently tuned items by the field, support and customers and it would be extremely helpful to allow the new values to be "set" but not yet applied until either a memcached restart occurs or a new node is balanced in. This is especially applicable for customers who are upgrading from a release that did not have these tunables and would want to change them after upgrading.

It would also be appropriate to display a warning message that the changes would not take effect until all nodes are either restarted or rebalanced out and in again.

 Comments   
Comment by Aleksey Kondratenko [ 15/Oct/14 ]
updated title to reflect that this specific ticket will only cover quick-and-simple solution which will be simple /diag/eval snippet to enable/disable this mode. No UI and no "proper" implementation is expected for 3.0.1
Comment by Aleksey Kondratenko [ 20/Oct/14 ]
http://review.couchbase.org/42311

Copying description from commit message:

Now if config variable dont_reload_bucket_on_cfg_change is set to
true, bucket instances on entire cluster will not be restarted on
bucket config change like bucket priority change or eviction policy
change.
Setting it can be done by posting:
ns_config:set(dont_reload_bucket_on_cfg_change, true).
to /diag/eval. End this mode can be disabled by setting variable to
false. Once disabled all bucket instances that need to be restarted
will restart.




[MB-12334] View Query timing out during Rebalance-in operation for DGM scenario Created: 13/Oct/14  Updated: 14/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 3.0.1
Fix Version/s: 3.0.1
Security Level: Public

Type: Bug Priority: Critical
Reporter: Parag Agarwal Assignee: Sriram Melkote
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Centos 6x, 3.0.0-1392Create 1 node cluster

10.6.2.144-146

Triage: Untriaged
Link to Log File, atop/blg, CBCollectInfo, Core dump: https://s3.amazonaws.com/bugdb/jira/MB-12334/10.6.2.144-10132014-1126-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-12334/10.6.2.145-10132014-1128-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-12334/10.6.2.146-10132014-1130-diag.zip
Is this a Regression?: Unknown

 Description   
1. Create 1 node cluster (10.6.2.144)
2. Create default buckets with 10K items
3. Create DGM Scenario for active_resident_threshold=60
4. Create 5 views
5. Rebalance-in 2 nodes (10.6.2.145,10.6.2.146) and build indexes in parallel

During Step 5 receiving error for query

Time out ERROR

Error occured querying view default_view0: {u'reason': u'timeout', u'from': u'http://10.6.2.146:8092/_view_merge/?stale=false&limit=10000&#39;}{u'reason': u'timeout', u'from': u'http://10.6.2.145:8092/_view_merge/?stale=false&limit=10000&#39;

Test Case::

./testrunner -i centos_x64--rebalance_out.ini get-cbcollect-info=True,get-logs=True,stop-on-failure=False,get-coredumps=True,force_kill_memached=False,verify_unacked_bytes=True,total_vbuckets=1024,std_vbucket_dist=8,chk_max_items=1000,chk_period=30 -t rebalance.rebalancein.RebalanceInTests.rebalance_in_with_queries,nodes_in=2,blob_generator=False,value_size=1024,active_resident_threshold=60,dgm_run=True,skip_cleanup=True,max_verify=10000,GROUP=IN

 Comments   
Comment by Aleksey Kondratenko [ 13/Oct/14 ]
Those timeouts are internal to view engine. From quick glance at logs I see nothing suspicious in logs.
Comment by Meenakshi Goel [ 14/Oct/14 ]
Observing similar errors during Views DGM tests on Windows with build 3.0.0beta-1382-rel
http://qa.hq.northscale.net/job/win_2008_x64--69_06_view_dgm_tests-P1/17/consoleFull




[MB-12333] how update syntax should look like? Created: 13/Oct/14  Updated: 14/Oct/14  Resolved: 14/Oct/14

Status: Closed
Project: Couchbase Server
Component/s: query
Affects Version/s: cbq-DP4
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Iryna Mironava Assignee: Gerald Sangudi
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Is this a Regression?: Unknown

 Description   
I have bucket b0 with 'b1' json document ({'name': 'John'})
I tried
cbq> update from b0 keys['b1'] set b0.name='123';
syntax error
cbq> update from b0 keys['b1'] set name='123';
syntax error
Not sure what's wrong

 Comments   
Comment by Gerald Sangudi [ 13/Oct/14 ]
update b0 keys ['b1'] set b0.name='123';

update b0 keys ['b1'] set name='123';

See https://github.com/couchbaselabs/query/blob/master/docs/n1ql-dml.md

Thanks.




[MB-12332] Top impacting keys Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 2.5.1, 3.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Patrick Varley Assignee: Aleksey Kondratenko
Resolution: Unresolved Votes: 0
Labels: customer, supportability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency

 Description   
We have seen cases where a few extremely large documents can have a big impact on a node even with a low number of operations. It would be good if we had a list like the "top keys" that tracked how impacting a key was on the node. It could use a very simple calculation such as: size of the document * the number of operations.

We could call it the ""Top impacting Keys". This will allow Admin's to track down rouge documents in the database.







[MB-12331] ep_num_locks fixed at 5, doesn't expand upon resize. Created: 13/Oct/14  Updated: 13/Oct/14

Status: Open
Project: Couchbase Server
Component/s: storage-engine
Affects Version/s: 2.5.0, 2.5.1, 3.0
Fix Version/s: None
Security Level: Public

Type: Task Priority: Major
Reporter: Dave Rigby Assignee: Chiyoung Seo
Resolution: Unresolved Votes: 0
Labels: