April showers bring May flowers, but until then it’s time for the April 2017 developer build.

The April 2017 Developer Build has a ton of bug fixes and feature enhancements, and we are one step closer to the stable release of Couchbase Server 5.0.

You can get the April 2017 developer build from the Couchbase downloads page in the developer tab.

April 2017 Developer Build

New platforms in April 2017 Developer Build

Based on the feedback we have received, here are some additional platforms that we are introducing starting with the April 2017 Developer Build. We hope you try out the April 2017 Developer Build on these platforms and give us your feedback!

  • Oracle Linux 7
  • Ubuntu 16.04
  • Windows Server 2016

Note that Ubuntu 12 is EOL this month, so future Couchbase releases will likely not support Ubuntu 12.

Bugs

Thank you for you feedback and helping us to identify and fix bugs for Couchbase Server 5.0. Here is a list of the critical and major bugs that were fixed in the April 2017 Developer Build.

Issue #

Description

MB-23102

[Ephemeral]: Fix the potential regression due to extra memory usage for sequential links in Stored Value

MB-23562

Ephemeral buckets: item count goes to -1

MB-23664

XDCR between ephemeral buckets gets stuck

MB-23055

[FTS] RBAC: Unable to create alias on an index created by the same user on sasl bucket

MB-23139

[FTS] moss compaction unit test assumes one particular segment impl

MB-23349

[FTS] up to 10x performance degradation when using large “query size” (limit) setting

MB-22870

[FTS] ephemeral: Docs not getting indexed when multiple indexes are present on an ephemeral bucket

MB-22871

[FTS] ephemeral: No docs indexed to a memory-only-index from ephemeral bucket

MB-23561

[FTS] moss store files are not deleted after compaction

MB-23674

[FTS] race detected in cbft

MB-21785

[FTS] UI: stats: the “items remaining” graph shows wrong data when KV mutations are in progress

MB-21783

[FTS] UI: stats: The “queries/sec” graph shows wrong data in FTS multi-node cluster setup

MB-21645

[FTS] slow query log conflicts with requirement to not log user data

MB-23227

couchbase server install fails on centos 6 machines

MB-23579

Windows Docker Container : service-stop.bat shuts down the container

MB-23517

Set → Remove → Set sequence of KV operations using the same key blocks the client connection

MB-23429

Auth failure with mem client for LDAP user

MB-23269

Memcached crashes when trying to write an audit event to a file with wrong permissions

MB-22691

ability to upsert the xattr key with any names depends on the keys already set in xattrs

MB-23347

Very low rate of insert operations due to lock contention

MB-23479

Query-select – can query any bucket

MB-23197

Addition of new node fails due to “Join completion call failed. Failed to start ns_server cluster processes back.”

MB-22759

N1QL insert/delete/update operations incorrectly authorized

MB-23758

Eliminate GO_DEFAULT_VERSION

MB-23372

Gap in covering array indexes

MB-23222

YCSB workload e with wrong n1ql syntax 100% memory is consumed

MB-23203

Index join chooses the wrong index and doesn’t choose the right index consistently.

MB-23186

Index Collation checks can’t use the API setting.

MB-23057

Scan is covered avoid IntersectScan

MB-23361

[N1QL] test_order_by_alias_aggr_fn functional test is failing

MB-23236

[N1QL RBAC]Incorrect message displayed when indexer storage mode is not set

MB-23179

[IndexAPI2] cbq engine panics with create index desc

MB-23049

cbq-engine constantly re-validates empty credentials

MB-23277

[n1ql rbac] The builtin user is getting updated when specifying a new role on a different bucket

MB-23245

[N1QL][CURL] Occasionally setting the connect-timeout option results in a panic

MB-23165

[N1QL] test_indexcountscan fails

MB-23132

CURL : Remove max-redirs option

MB-23101

Restrict the limit pushdown on IntersectScan(s)

MB-23219

investigate query logging if there is a parser crash.

MB-23134

CURL – Disable all other protocols except HTTP/HTTPS

MB-22994

[N1QL]Query with predicates on 3 different fields with OR clause does not use UnionScan

MB-23610

[N1QL][Monitoring] Cannot delete/filter system:completed_requests by node

MB-23723

request_plus range queries with LIMIT are slow

MB-23716

N1QL: test_array_index_regexp_covering fails,query with regular expression times out on centos and windows,panic seen in query.log

MB-21971

Expose meta().cas and meta().expiration to N1QL

MB-22874

jdbc-json driver throws nullpointer exception with YCSB workload

MB-23106

panic found in indexer

MB-22920

Intermittent failure:”Index scan timed out”

MB-22879

Throughput of composite queries with TOKENS() dropped from ~24K to ~4K queries/sec

MB-23729

Initial indexing of 200M items increased from 6 minutes to 1 hour

MB-23657

Q2, Q3, and YCSB Workload E throughput dropped to 400 queries/sec

MB-22982

Tree form query output fails to print in query workbench

MB-23311

cbbackupmgr crashes with “fatal error: concurrent map read and map write”

MB-23490

Changing the password of user from a particular session should invalidate other sessions

MB-23280

[UI]Authentication Source is not selected for a ldap user

MB-23016

[FTS UI] Rebalance progress indicator doesn’t show granular level progress

MB-23437

[UI] Not able to set Index Storage settings on the Index Node at setup time

MB-23085

View Engine not detecting meta.id if doc has xattrs

MB-23423

Memcached connection closed for no apparent reason after a couple minutes

MB-22997

Fix deadlock issue in when closing upr stream

MB-23228

Avoid frequent replication restart when node is removed from target cluster

MB-23728

Remote cluster ref cannot rotate on target nodes when target is elastic search

We still want your feedback!

Stay tuned to the Couchbase Blog for information about what’s coming in the next developer build.

Interested in trying out some of these new features? Download Couchbase Server 5.0 April 2017 Developer Build today!

The 5.0 release is fast approaching, but we still want your feedback!

Bugs: If you find a bug (something that is broken or doesn’t work how you’d expect), please file an issue in our JIRA system at issues.couchbase.com or submit a question on the Couchbase Forums. Or, contact me with a description of the issue. I would be happy to help you or submit the bug for you (my Couchbase handlers let me take selfies on our cartoonishly big couch when I submit good bugs).

Feedback: Let me know what you think. Something you don’t like? Something you really like? Something missing? Now you can give feedback directly from within the Couchbase Web Console. Look for the feedback icon icon at the bottom right of the screen.

In some cases, it may be tricky to decide if your feedback is a bug or a suggestion. Use your best judgement, or again, feel free to contact me for help. I want to hear from you. The best way to contact me is either Twitter @mgroves or email me matthew.groves@couchbase.com.

Posted by Matthew Groves, Developer Advocate

Matthew is a Developer Advocate for Couchbase, and lives in the Central Ohio area. He has experience as a web developer as a consultant, in-house developer, and product developer. He has been a regular speaker at conferences and user groups all over the United States, and he has written AOP in .NET for Manning Books. He has experience in C# and .NET, but also with other web-related tools and technologies like JavaScript and PHP. You can find him on Twitter at @mgroves.

Leave a reply