Bug 1583853

Summary:	TokuDB can't be built against Jemmaloc 5
Product:	[Fedora] Fedora	Reporter:	Michal Schorm <mschorm>
Component:	mariadb	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	28	CC:	alice, dciabrin, hhorak, jstanek, mbayer, mkocka, mmuzila, mschorm, praiskup
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-28 22:27:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Schorm 2018-05-29 21:56:59 UTC

The TokuDB storage engine does not support Jemalloc 5 yet.
However there is only Jemalloc 5 in F>=28

Percona upstream tracker:
https://jira.percona.com/browse/PS-4393

--

Following solutions comes up my mind:
* do not build TokuDB subpackage on F>=28
 - can create problems on upgrades and updates
 - for example: #1538870
* build TokuDB without Jemalloc
 - this combination is not supported and the upstream says it explicitly
* build against some jemmaloc compat stream
 - jemalloc-compat package? a module?
  - is it even possible? Is it worth the work needed to be done?

Comment 1 Jan Kurik 2018-08-14 10:56:09 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 2 Michal Schorm 2018-09-18 08:54:28 UTC

This issue is applicable for F>=28.

The MariaDB upstream is blocked by TokuDB upstream in this case:

MariaDB ticket:
https://jira.mariadb.org/browse/MDEV-15034

Comment 3 Ben Cotton 2019-05-02 20:54:56 UTC

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 22:27:58 UTC

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.