[SERVER-27687] ppc64le build incorrectly indicates pointer size of 32 Created: 14/Jan/17  Updated: 15/Aug/17  Resolved: 07/Apr/17

Status: Closed
Project: Core Server
Component/s: Internal Code, Portability, Replication
Affects Version/s: 3.2.11
Fix Version/s: 3.2.13, 3.4.4, 3.5.6

Type: Bug Priority: Major - P3
Reporter: Mark Helmstetter Assignee: Jonathan Reams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2
Sprint: Platforms 2017-03-06, Platforms 2017-04-17
Participants:

 Description   

Using MongoDB Enterprise on Power RHEL 7.2 ppc64le build, the oplog size is defaulting to 50MB. The data volume is 50GB, as such the oplog size should have defaulted to 2.5GB.



 Comments   
Comment by Githook User [ 07/Apr/17 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: SERVER-27687 Fix cpuAddrSize detection on Linux for hostInfo command

(cherry picked from commit d2211f33b794dc638bec61a14ae9ba68e76b8946)
Branch: v3.2
https://github.com/mongodb/mongo/commit/298bfdb518fd202c59864dec1390ffcc730a626b

Comment by Githook User [ 07/Apr/17 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: Revert "SERVER-27687 Fix cpuAddrSize detection on Linux for hostInfo command"

This reverts commit 8b57003ddf5c89774d49d02028c18deec284a3db.
Branch: v3.2
https://github.com/mongodb/mongo/commit/6129d7a67e46e41efdd1a7050e6a189df592f126

Comment by Githook User [ 07/Apr/17 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: SERVER-27687 Fix cpuAddrSize detection on Linux for hostInfo command

(cherry picked from commit d2211f33b794dc638bec61a14ae9ba68e76b8946)
Branch: v3.2
https://github.com/mongodb/mongo/commit/8b57003ddf5c89774d49d02028c18deec284a3db

Comment by Githook User [ 07/Apr/17 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: SERVER-27687 Fix cpuAddrSize detection on Linux for hostInfo command

(cherry picked from commit d2211f33b794dc638bec61a14ae9ba68e76b8946)
Branch: v3.4
https://github.com/mongodb/mongo/commit/0072cd5d0c15e8721c3055928ee5b08709097350

Comment by Githook User [ 06/Apr/17 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: SERVER-27687 Fix cpuAddrSize detection on Linux for hostInfo command
Branch: master
https://github.com/mongodb/mongo/commit/d2211f33b794dc638bec61a14ae9ba68e76b8946

Comment by Jonathan Reams [ 27/Mar/17 ]

Fixing the address size in the linux implementation of ProcessInfo isn't hard, but I'm not sure why we have this function at all. It's only really used when setting the default size of the oplog (we also send it as an informational message in the hostInfo command). We also have an #ifdef to do special sizing on apple machines. I'll put up a code review to fix the processInfo for now, but this really seems like a replication bug.

Comment by Eric Milkie [ 13/Feb/17 ]

The determination of "32-bit pointer size" is incorrect in the code; it is looking for "x86_64" in the uname of the server.
In addition, since 32-bit builds are no longer supported, we should simply remove the special code for choosing a smaller oplog size (it is the only thing in the system that looks at pointer size).

Generated at Thu Feb 08 04:15:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.