I also tried olcIndexIntLen: 4
But it’s still the same From: Maud Parratt <maud.parr...@bjss.com> Date: Friday, 21 July 2023 at 12:01 To: Howard Chu <h...@symas.com>, Quanah Gibson-Mount <qua...@fast-mail.org>, openldap-technical@openldap.org <openldap-technical@openldap.org> Subject: Re: slapindex a 60GB mdb in reasonable time I’ve configured my arm64 instance with: dn: cn=config olcIndexHash64: FALSE The indexes are still broken though, is this the configuration you’re referring to? Given my mdb is from an amd64 box, it’ll be 32 bit, so I want to match the configuration. From: Howard Chu <h...@symas.com> Date: Thursday, 20 July 2023 at 20:38 To: Quanah Gibson-Mount <qua...@fast-mail.org>, Maud Parratt <maud.parr...@bjss.com>, openldap-technical@openldap.org <openldap-technical@openldap.org> Subject: Re: slapindex a 60GB mdb in reasonable time Quanah Gibson-Mount wrote: > > > --On Thursday, July 20, 2023 7:13 PM +0100 Howard Chu <h...@symas.com> wrote: > >>> Pretty sure they're not compatible. I.e., you must load from LDIF when >>> switching architectures. >> >> There's no particular reason for arm64 and amd64 to be incompatible, >> they're both 64bit little-endian. arm64 and x86 (32bit) would most likely >> be incompatible though. > > > Hm, not different page sizes perhaps? But if this is 64-bit on both ends, > and the amd64 generated index databases don't work on ARM64, seems to indicate > something's not compatible? I just checked on a local box. My ARM64 build defaulted to 64bit index keys, the AMD64 build used 32bit index keys. Not sure why the defaults are different, but configuring 64bit index keys on the AMD64 box would fix this. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, 1 Whitehall Quay, Leeds, LS1 4HR
