MongoDB 3.2.10 is out and is ready for production deployment. This release contains only fixes since 3.2.9, and is a recommended upgrade for all 3.2 users.
Fixed in this release:
- SERVER-12048 Calling "service mongod start" with mongod running prevents "service mongod stop" from working
- SERVER-16801 Update considers a change in numerical type to be a noop
- SERVER-20306 75% excess memory usage under WiredTiger during stress test
- SERVER-24885 The systemd MaxTasks feature can prevent mongod from accepting new connections
- SERVER-24971 Excessive memory held by sessions when application threads do evictions
- SERVER-25478 Use wtimeout in sh.setBalancerState
- SERVER-25951 Report additional metrics in getMore slowms logging
- SERVER-25974 Application threads stall for extended period when cache fills
- TOOLS-1429 mongostat panic when monitored server is restarted
- WT-2026 Maximum pages size at eviction too large
- WT-2924 Ensure we are doing eviction when threads are waiting for it
As always, please let us know of any issues.
-- The MongoDB Team
MongoDB at DevFest DC 2016
Being a Technical Account Manager with MongoDB's Cloud Team often means getting an opportunity to meet great new people and reconnect with familiar faces. I was recently invited by the Google Dev Group in Washington DC to come and discuss MongoDB at DevFest DC 2016. While the world is fairly knowledgeable of the explosive technology scenes in Silicon Valley and New York City, the DC area should be praised for drawing some of the best talent in the industry, evidenced by the caliber of the speakers and the attendees. The Capital One HQ in McClean, VA was host to two days of developer and technology information sharing. Our friend Chida Sadayappan helped ensure that everyone was able to feed their minds, their bellies, and hopefully their bags with some neat swag. Full houses were the norm in the auditoriums as a lineup of speakers from Google, Capital One, The Washington Post and, of course, MongoDB presented on a range of subjects. [Photo Credit](https://twitter.com/zugaldia/status/779314760101879808) Listening to experts from the DC area like Jessica Bell, Mark Brown and Lougenia Bailey discuss the more esoteric subjects of diversity in technology and imposter syndrome was tremendous. One of the encouraging aspects of events like this is the move beyond live demos and code samples to explore the human aspects of being a contributor in a team of developers. As the day progressed, there were opportunities to eat snacks, meet people, and work in code labs. Technologies like Kubernetes took front and center in code labs as attendees looked for ways to best leverage the Google Compute Engine for their apps. Later in the day, I got an opportunity to do my Jumpstart MongoDB: What You Need to Know talk for a full room of developers and technology enthusiasts. I did my best in about 40 minutes to give attendees a brief introduction to how they can begin using MongoDB quickly. The room stayed full until the very end as I finished my talk with a gift —each member of the audience received a $100 credit to use MongoDB Atlas, our fully hosted database as a service. I took a few questions which mostly centered around subjects like sharding and migrating from relational databases. [Photo Credit](https://twitter.com/darunreddy/status/779852922683322368) The day wrapped up for me and it was time to head back on the train for NYC. It was really a pleasure to get an opportunity to meet some new friends, run into some old ones, and share a little bit of the love we have for MongoDB Atlas. We're always happy to meet current and future MongoDB users at various events across the globe. To get a full list of where we'll be next, check out our events page: View all MongoDB events About the author - Jay Gordon Jay is a Technical Account Manager with MongoDB and is available via our chat to discuss MongoDB Cloud Products at https://cloud.mongodb.com
Solving Customer Challenges: Meet Consulting Engineer Paul-Emile Brotons
Our Professional Services team is growing. Hear from Paul-Emile Brotons about his Consulting Engineer (CE) role, the types of projects he works on for customers, how he continually learns, and what makes this role a great opportunity for people with technical backgrounds who enjoy solving a variety of problems. Jackie Denner: Thanks for sharing your experience as a Consulting Engineer. Can you tell me about the Consulting Engineer team within Professional Services at MongoDB? Paul-Emile Brotons: I joined MongoDB a year and a half ago. The Consulting Engineering team is responsible for assisting customers at every stage of their MongoDB journey to ensure they are successful. We assist customers with training, database design, architecture design, code reviews, preproduction audits and reviews, setup, and health checks. I’m part of the South European team and I’m based out of Paris, but the Consulting Engineering team is worldwide. Since we are solving challenging problems, the team is very close and meets daily to share ideas and discuss solutions. I always have colleagues available to help at any time of day. JD: As a junior engineer, why did you opt for a Consulting Engineer role instead of a traditional Product Engineer role? PEB: Before joining MongoDB, I was a full-stack engineer at a French startup specializing in revenue management. I learned great technical skills there, but, in the end, I felt I was missing the big picture: What other stacks exist on the market? What tools are other engineering teams at big companies or startups working with? That is exactly what the Consulting Engineer role made possible for me. Since our projects are usually short-term, a typical CE may see 50 projects in a year. In my current role, I have been working with almost every new and exciting technology. I also get to learn how people within product and engineering work in other organizations. I find this very valuable, and it’s not something you can easily find in a traditional Product Engineer role. JD: What does a day in your role look like? PEB: CEs are assigned to “missions,” which typically range from one to four days and concern a specific customer. Longer-term projects can span several months. My role generally starts the week before. Before each mission, I try to set up a short preconsult session where I meet with customers and discover the topics they want to discuss. Then, on the day of the mission, I provide training, performance evaluation, tuning, and more. I learn a lot in my role, and I try to find solutions to all the difficult problems the customer has not been able to solve alone. It’s challenging and very rewarding. In some cases, I may not be assigned to a customer and I will be working on preparation and continuous learning. I appreciate the liberty my role gives me. JD: What was your onboarding like, and what learning and growth opportunities are there on the Consulting Engineer team? PEB: To be completely honest, I was a bit scared when I joined. I was very impressed with the way people work here, and I had a feeling it would be hard for me to onboard. However, the ramp-up process is so well-done that it almost felt easy. The first weeks were dedicated only to training. First, we have to learn a lot about MongoDB. A CE is a database expert. Since almost every software needs a persistent layer, this expertise is very valuable. Second, we have to know our stuff when it comes to Linux, networking, cloud providers, architecture, coding, and more. Afterward, everything is done to gradually increase the level of difficulty; complex missions are not delivered by new hires. Management is really careful about that, which is reassuring. Once a CE is performing well in their role, they may be promoted to Senior and then Principal grades. Many of us also study to pass certifications. I will soon start studying for a Linux sysadmin certification. The management team is very supportive and encourages continuous learning. JD: How do you interact with other teams at MongoDB? PEB: The CE role requires a lot of interaction with teams such as Sales, Presales Engineering, and Product Engineering. Consulting Engineers can be leveraged to help Sales and Solution Architects before the sale happens, since we are seen as trusted advisers. We also often speak to product teams to discuss the inner workings of a product, feature, or system. I’ve had the opportunity to meet many people within MongoDB. JD: What is one of the most interesting or challenging projects you’ve worked on? PEB: It is honestly difficult to choose, but I would pick a long project I worked on with a major container transportation and shipping company. It was challenging given the scope of the project and the number of interactions and subjects I had to deal with. The project was key for the customer, and it was technically demanding. We had to review the whole application architecture; analyze the front end to infer the requests and schema design needed on the database side; work with a wide range of professionals, including developers, solution architects, Linux engineers, and project managers; and test that everything would happen as expected. It was a great learning experience, from both a personal and professional perspective. JD: What makes someone successful in a CE role? PEB: Aside from sufficient knowledge of computer science, the CE role requires good communication and problem-solving skills. You have to know how to listen to and understand the problems customers encounter before you can think of a solution. Good customer contact is often the key to a mission’s success, and it makes the difference between a satisfied customer and a happy customer. JD: What advice would you offer someone looking to move into Professional Services at MongoDB? PEB: First, prepare well for the interviews — study up on algorithms, two programming languages, and basic database and hardware concepts. The interviews can be challenging, and there are a lot of rounds. Second, I would advise candidates to look at the beginners course on the MongoDB University website. The courses are free and they’re the best I have done on the web so far. Going deeper into learning MongoDB before joining the company saved me a lot of time. Last but not least, I would encourage candidates to contact CEs at MongoDB to get a clear view of the company and the role. My colleagues and I are more than happy to answer any questions that might help someone decide if this role is the right fit for them. Interested in a Professional Services career at MongoDB? We have several open roles on our team and would love for you to transform your career with us!