[MCOL-4554] Fix Jemalloc Dependency Issue Created: 2021-02-23  Updated: 2021-04-19  Resolved: 2021-04-19

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Blocker
Reporter: Todd Stoffel (Inactive) Assignee: Roman Navrotskiy
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-24124 MariaDB Server sources contain binary... Closed
Sprint: 2021-4, 2021-5, 2021-6

 Description   

Currently we insert the shared object file libjemalloc.so.2 in /var/lib/columnstore. This was a work around due to the fact that jemalloc was only included in the epel-release repo for RedHat derivatives (CentOS, Fedora). A customer without external internet access may not have had a way to connect with this "extra packages" repo.

dbart has agreed to begin syncing this RPM package from epel-release into the official MariaDB Community and Enterprise repos. This will allow us to call this RPM as a dependency for MariaDB-columnstore-engine and have the shared object available in the correct default location /usr/lib64

In fact, this looks to already be in place for community: https://downloads.mariadb.com/MariaDB/mariadb-10.5.9/yum/centos/7/x86_64/rpms/

This is going to require a change to the MariaDB-columnstore-engine RPM package as well as a possible change to the path in which Columnstore looks for jemalloc.



 Comments   
Comment by Gregory Dorman (Inactive) [ 2021-02-25 ]

ben.thompson and David.Hall I am not sure who is in the better position to do our part (once Bartholomeo did his, as in MENT-1115).

Theoretically, we should be able to do it even before the curtain tomorrow, but maybe it is too sudden. Let me know if we can do it for 5.5.2, even if it means another ref update next week. As per toddstoffel, this needs change in package composition, as well as possibly some code and some paths inside.

Generated at Thu Feb 08 02:51:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.