[SERVER-28093] MongoDB 3.4 fails to start with Illegal instruction on s390x z12 Created: 24/Feb/17 Updated: 31/May/17 Resolved: 28/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.0, 3.4.1, 3.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Höller | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | |||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||
| Steps To Reproduce: | Download the mongodb sourses and untar them:
|
|||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||
| Description |
|
MongoDB fails to start on an zSeries 12 with rhel72. The same source works perfectly well on a z13 machine. The difference between z12 and z13 is quite big, since the were a lot of change in the zSeries intstruction set. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 14/Mar/17 ] |
|
Hi Michael - If you have the opportunity, it would be great if you could confirm that 3.4.3-rc1 runs correctly in your z12 environment, as that would confirm that the issue originally raised here (and in https://downloads.mongodb.com/linux/mongodb-linux-s390x-enterprise-rhel72-3.4.3-rc1.tgz Subsequently, when we issue a 3.4 release containing the fix for I hope your performance investigations re MongoDB on zSeries are going well. |
| Comment by Michael Höller [ 13/Mar/17 ] |
|
Hi, no worries - I realized that. I still owe you a test. Unfortunately I am kind of "locked" in Think Tank the last and next week. All the best |
| Comment by Andrew Morrow (Inactive) [ 13/Mar/17 ] |
|
Michael - Apologies, I got that wrong. I expect the fix for |
| Comment by Andrew Morrow (Inactive) [ 13/Mar/17 ] |
|
Hi Michael - Yes, that is the ticket to watch. I would expect that the fix will arrive in the MongoDB 3.4.3 release (3.4.2 is not yet out, but I don't think the fix will make that release as it has already gone to a release candidate). |
| Comment by Michael Höller [ 04/Mar/17 ] |
|
Hello Andrew, I am fine to close this ticket when you have already one. Can you please provide me the link to this one? I will do some tests and provide information as far as I can since I am under a NDA... Thanks a lot |
| Comment by Andrew Morrow (Inactive) [ 28/Feb/17 ] |
|
Michael - I'm going to close this ticket as a duplicate, since we have other tickets that are tracking this work. Please feel free to re-open it if you have any additional comments, or if the nightly build that I've provided doesn't solve the issue for you. If you find interesting things in your performance testing, please feel free to open new tickets. |
| Comment by Andrew Morrow (Inactive) [ 24/Feb/17 ] |
|
Hi Michael - You can download a nightly build of the s390x RLEH 7.2 build here: https://s3.amazonaws.com/mciuploads/mongodb-mongo-v3.4/enterprise-rhel-72-s390x/131e03e5dc4fa94d44f600d2844b470ede4f1d4e/binaries/mongo-mongodb_mongo_v3.4_enterprise_rhel_72_s390x_131e03e5dc4fa94d44f600d2844b470ede4f1d4e_17_02_17_14_50_40.tgz Of course, the usual caveats apply - this is a nightly build so is not suitable for production use, etc. Note that if you are doing performance testing and your benchmark system is not a z13 system, this or the upcoming 3.4.3 release should be fine to use for benchmarking, because it never could have taken advantage of the VX extensions for CRC32C in the first place. We are happy to help, and if you have any interesting results from your performance testing, please let us know. |
| Comment by Michael Höller [ 24/Feb/17 ] |
|
Hello Andrew, Thanks a lot |
| Comment by Andrew Morrow (Inactive) [ 24/Feb/17 ] |
|
Hi - This is a known issue. The RHEL 7.2 build of MongoDB 3.4 is intended to run on z12, but there is bug that introduces a hard dependency on the z13 only VX instructions, which we use for hardware accelerated CRC32C support in the WiredTiger storage engine. To work around this issue, we have temporarily disabled hardware CRC32 support in all zSeries builds in If you are doing testing or qualification and a non-production build would be useful for you, we can provide instructions on how to obtain a nightly build of the v3.4 branch that contains the fix that will be delivered in the upcoming 3.4.3 release. If possible, we would also appreciate your testing the build to ensure that it works around the bug on your affected system. |