MongoDB 3.2.0-rc6 is out and is ready for testing. This is the culmination of the 3.1.x development series.
Fixed in this release candidate:
- SERVER-21726 WiredTiger primaries replicate no-op update, leading to out-of-sync secondaries and data loss
- SERVER-21115 Add dbHash checking to concurrency suite
- SERVER-21711 make currentJSExceptionToStatus more robust
- SERVER-21690 Text Search - Performance Regression in 3.2.0 RC4
- SERVER-21553 Oplog grows to 3x configured size
As always, please let us know of any issues.
– The MongoDB Team
Call for Papers Open for MongoDB World 2016
Call for Papers open until December 18th. Tell us your transformational story We want to hear your GIANT ideas at MongoDB World 2016. Submit your papers now through December 18th and tell us how you’ve launched transformative projects, defeated technical obstacles, and achieved GIANT scale with MongoDB. 12.18 Call for Papers Closes 01.15 Proposers Notified 02.15 Outline Due 03.11 1st Draft Due 04.15 2nd Draft Due 04.25 Speaker rehearsal completed 05.31 Final Slides Due </tr> What we’re looking for We’re excited to include fascinating stories that stretch across a wide range of topics, from differing backgrounds and technical professions. These fields include: Developers Operations CIOs CTOs QA engineers System administrators Data analysts Business architects and more. The selection process We are accepting proposals until December 18, 2015. Our selection committee will review and reply to proposals by January 15, 2015. All proposals and speakers must abide by the conference Code of Conduct . Learn more To learn more about submitting your talk to MongoDB World 2016 visit our information page . Submit your talk
Vector Search and Dedicated Search Nodes: Now in General Availability
Today we’re excited to take the next step in adding even more value to the Atlas platform with the general availability (GA) release of both Atlas Vector Search and Search Nodes. Since announcing Atlas Vector Search and dedicated infrastructure with Search Nodes in public preview, we’ve seen continued excitement and demand for additional workloads using vector-optimized search nodes. This new level of scalability and performance ensures workload isolation and the ability to better optimize resources for vector search use cases. Atlas Vector Search allows developers to build intelligent applications powered by semantic search and generative AI over any data type. Atlas Vector Search solves the challenge of providing relevant results even when users don’t know what they’re looking for and uses machine learning models to find results that are similar for almost any type of data. Within just five months of being announced in public preview, Atlas Vector Search has already received the highest developer net promoter score (NPS) — a measure of how likely someone is to recommend a solution to someone else — and is the second most widely used vector database, according to Retool’s State of AI report . There are two key use cases for Atlas Vector Search to build next-gen applications: Semantic search: searching and finding relevant results from unstructured data, based on semantic similarity Retrieval augmented generation (RAG): augment the incredible reasoning capabilities of LLMs with feeds of your own, real-time data to create GenAI apps uniquely tailored to the demands of your business. Atlas Vector Search unlocks the full potential of your data, no matter whether it’s structured or unstructured, taking advantage of the rise in popularity and usage of AI and LLMs to solve critical business challenges. This is possible due to Vector Search being part of the MongoDB Atlas developer data platform, which starts with our flexible document data model and unified API providing one consistent experience. To ensure you unlock the most value possible from Atlas Vector Search, we have cultivated a robust ecosystem of AI integrations, allowing developers to build with their favorite LLMs or frameworks. Our ecosystem of AI integrations for Atlas Vector Search To learn more about Atlas Vector Search, watch our short video or jump right into the tutorial . Atlas Vector Search also takes advantage of our new Search Nodes dedicated architecture, enabling better optimization for the right level of resourcing for specific workload needs. Search Nodes provide dedicated infrastructure for Atlas Search and Vector Search workloads, allowing you to optimize compute resources and fully scale search needs independent of the database. Search Nodes provide better performance at scale, delivering workload isolation, higher availability, and the ability to better optimize resource usage. In some cases we’ve seen 60% faster query time for some users' workloads, leveraging concurrent querying in Search Nodes. In addition to the compute-heavy search nodes we provided in the public preview, this GA release includes a memory-optimized, low CPU option that is optimal for Vector Search in production. This makes resource contention or the possibility of a resulting service interruption (due to your database and search sharing the same infrastructure previously) a thing of the past. Coupled Architecture (left) compared with the decoupled Search Node architecture (right) We see this as the next evolution of our architecture for both Atlas Search and Vector Search, furthering the value provided by the MongoDB developer data platform. At this time Search Nodes are currently available on AWS single-region clusters (with Google Cloud and Azure coming soon), as customers can continue using shared infrastructure for Google Cloud and Microsoft Azure. Read our initial announcement blog post to view the steps of how to turn on Search Nodes today, or jump right into the tutorial . Both of these features are available today for production usage. We can’t wait to see what you build, and please reach out to us with any questions.