[SERVER-30121] Solaris port for MongoDB 3.4.6 and newer Created: 13/Jul/17 Updated: 06/Dec/22 Resolved: 30/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 3.4.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Heitepriem | Assignee: | Backlog - Build Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Build
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Hi everyone, I noticed that the Download of MongoDB 3.4.6 for Solaris is missing on the Download page (https://www.mongodb.com/download-center?jmp=nav). When selecting the "Solaris" tab nothing happens and also the direct link (https://fastdl.mongodb.org/sunos5/mongodb-sunos5-x86_64-3.4.6.tgz) results in a 404-error. Thanks in advance. Best regards, |
| Comments |
| Comment by Alyson Cabral (Inactive) [ 30/Aug/17 ] |
|
Closing this ticket and we will continue our follow-up conversation off JIRA. |
| Comment by Daniel Heitepriem [ 30/Aug/17 ] |
|
Hi alyson.cabral, thank you very much for this explanation. Your decision is comprehensible. We have to discuss internally how to proceed with this situation but I suppose that we either have to switch all our servers to another OS (king of a big task with ~30 productive servers) or just deploy a separate database cluster using a common linux distribution (preferable) Regards, P.S.: I suppose this issue can be closed |
| Comment by Alyson Cabral (Inactive) [ 29/Aug/17 ] |
|
Hi semirben, I'm Aly Cabral, one of our Product Managers here at MongoDB. After careful thought and data analysis, we have decided to discontinue our support of Solaris. We simply haven't been able to justify the engineering cost of maintaining our support. You may have seen Andrew's blog post on our Farewell to Solaris which goes deeper into the reasons behind our decision. That being said, we value our users and want to support you as best we can. I'd like to schedule a conversation with you to go into the reasons behind your continued use of Solaris and see if we can personally offer any help transitioning away from the operating system. Please look out for an email from me with further details. Aly Cabral |
| Comment by Ramon Fernandez Marina [ 14/Jul/17 ] |
|
semirben, I'm updating the summary of this ticket and repurposing it as a request for us to continue to release Solaris versions of MongoDB releases. Apologies for any inconvenience this may be causing you, and thanks for the additional details on your plans around MongoDB on Solaris. Regards, |
| Comment by Andrew Morrow (Inactive) [ 14/Jul/17 ] |
|
semirben - Thank you for providing that information. We will update this ticket when we have more information to share regarding the availability of Solaris releases for 3.4. |
| Comment by Daniel Heitepriem [ 13/Jul/17 ] |
|
Hi acm, Solaris is the main and only OS on our servers (mainly i386 hardware and a few SPARC servers). We are using this for productive environments with multi-million transactions. We are planning to stay with Solaris. At the moment we are migrating all our Solaris 10 hosts to Solaris 11.3. MongoDB is used in version 2.6 on older hosts and the current 3.4 version on our Solaris 11 hosts. Our databases on Solaris 11 run with the WiredTiger storage engine and the older ones with MMapV1. Regards, |
| Comment by Andrew Morrow (Inactive) [ 13/Jul/17 ] |
|
Hi semirben - Thank you for your report. Unfortunately the Solaris builds are unavailable for the most recent releases across the 3.2, 3.4, and master branches. Due to ongoing operational problems with our Solaris infrastructure that affected our ability to issue releases on that platform, we were faced with the unpleasant situation of either holding all releases on all platforms until the Solaris release issues were resolved, which would have delayed critical bug fixes from shipping, or not issuing the Solaris releases for the most recent versions. Neither was a particularly good choice, but we felt on balance that it was more important to ship critical bug fixes to our Windows, Linux, and macOS users in a timely fashion. We are working to understand the cause of the Solaris issues and our current plan is to restart Solaris releases for 3.2 and 3.4 once we have a fix in place. However, please be aware that we are also having internal discussions as to the long term plan regarding Solaris. Our data indicates that only a tiny fraction of our users run on Solaris. In addition, the overall health of the Solaris ecosystem seems in steep decline. While this discussion and our operational problems on the platform are coincidental, these problems have certainly informed the recent discussion. Overall, our current leaning is to discontinue Solaris releases in the near future. Therefore, we are very interested to know more about those users who identify a need for MongoDB running on Solaris, as you have. We would appreciate it greatly if you could let us know more about how you are using Solaris, whether you are planning to stay with the platform or are planning to migrate off (and, if so, to what?), which of the many variants of Solaris you are running in production, what version(s) of MongoDB you are running and with what storage engines, etc. Thanks, |