[SERVER-42427] Upgrade MozJS/Spidermonkey to ESR 91 Created: 25/Jul/19  Updated: 06/Feb/24  Resolved: 08/Mar/22

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Backlog - Query Execution
Resolution: Duplicate Votes: 10
Labels: move-sdp, qexec-team, third-party-upgrade
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-50115 arm64/aarch64 support for macOS Closed
Duplicate
duplicates SERVER-47276 Evaluate upgrade of Spidermonkey to E... Closed
duplicates SERVER-61008 Upgrade MozJS Closed
is duplicated by SERVER-47276 Evaluate upgrade of Spidermonkey to E... Closed
Related
related to SERVER-64312 Complete TODO listed in SERVER-42427 Closed
is related to SERVER-64574 Upgrade MozJS/Spidermonkey to the lat... Backlog
Assigned Teams:
Query Execution
Participants:

 Description   

This ticket encompasses the work to upgrade MozJS/Spidermonkey to the latest version as decided by product and engineering for query and build.



 Comments   
Comment by Garrett Leonard (Inactive) [ 16/Dec/21 ]

Disregard. Moved to the forum.

Comment by Andrew Morrow (Inactive) [ 14/Dec/21 ]

continuities@gmail.com - The docker configuration in your link is not maintained by us, so I don't think we are in a position to directly address any issues it may have with MongoDB 5.0. And while we would certainly like to help investigate, this ticket isn't the right forum. I see that you started a thread on https://www.mongodb.com/community/forums/t/mongo-5-on-apple-m1-laptops and we can continue the discussion there.

Comment by Michael Townsend [ 14/Dec/21 ]

Oh you're right! It is a Docker warning
[https://github.com/docker-library/mongo/issues/485#issuecomment-891991814
]

I've just rolled back to 4.4 until this gets fixed; but that the official mongodb docker image doesn't work on M1 macbooks is a pretty serious issue, I think. Please please please prioritise this ticket.

Comment by Andrew Morrow (Inactive) [ 12/Dec/21 ]

continuities@gmail.com - The ticket where we backed out the AVX requirement on macOS to allow for Rosetta 2 is SERVER-56728. As long as your 5.0 containers are running 5.0.0-rc0 or newer, it should be fine. The observed behavior on Rosetta 2 without the fix for SERVER-56728 was an illegal instruction. I wouldn't expect binaries with AVX to be able to get off the ground enough to even start logging, and I don't think we added any logging about AVX support. Perhaps that message is from Docker itself? It is always possible that somehow Docker is getting in the way here. What happens if you try to start the same MongoDB version directly on the M1 machine, rather than within Docker? Feel free to open a new ticket with details if you continue to have problems here and I'll be happy to investigate with you.

Comment by Michael Townsend [ 11/Dec/21 ]

Is this the case when running inside a docker container? My Mongo5 containers never become connectable since I switched to an M1-based development machine, and the only message in the logs is a complaint about AVX.

Comment by Andrew Morrow (Inactive) [ 11/Dec/21 ]

continuities@gmail.com  - The AVX requirement doesn't yet apply for MongoDB 5.0+ on macOS, exactly so that Rosetta 2 can continue to operate while we work on the MozJS upgrade. Once we have MozJS upgraded, we will probably restore the requirement.

Comment by Michael Townsend [ 11/Dec/21 ]

Unless I am mistaken, Rosetta 2 is no longer an option with Mongo5 because of the AVX requirement, which Rosetta does not simulate.

Comment by Arshabh Agarwal [ 22/Sep/21 ]

Frankly, we did not explore Rosetta 2. Thanks for the tip. We will explore rosetta and see if it meets our needs. However, it is always good to use binaries made for the native system vs. using a translation environment like Rosetta. So will keep watching this issue - even if Rosetta helps

Comment by Andrew Morrow (Inactive) [ 22/Sep/21 ]

arshabh.agarwal@inspectlogs.com - It should be possible to run the x86_64 binaries on M1 macbooks via Rosetta 2. Is there a reason that solution isn't available for you or doesn't meet your needs?

Comment by Arshabh Agarwal [ 22/Sep/21 ]

Hi Andrew,

We are trying to use mongodb-kubernetes-operator (community) to run replica set in our kubernetes cluster. However the operator depends on this task before they can provide support for arm64/aarch64 on Mac OS.

https://jira.mongodb.org/browse/SERVER-50115

We are using Apple Silicone M1 macbooks and cannot use the operator on these machines right now

Comment by Andrew Morrow (Inactive) [ 22/Sep/21 ]

arshabh.agarwal@inspectlogs.com - The upgrade is complex, but we are working on it. Unfortunately, at this time we are not ready to provide an estimate on when we will have a stable release that offers the upgrade. May I ask though why you are particularly awaiting it?

Comment by Arshabh Agarwal [ 21/Sep/21 ]

@Andrew Morrow - ESR 91 has been released last month. Any plans on when will this upgrade take place ?

Comment by Andrew Morrow (Inactive) [ 08/Jul/21 ]

The earliest ESR that meets our requirement for Apple Silicon support will be ESR 91, per https://hacks.mozilla.org/2021/01/porting-firefox-to-apple-silicon/#comment-26808. That release is expected on August 8th, per https://wiki.mozilla.org/Release_Management/Calendar.

Generated at Thu Feb 08 05:00:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.