[Maria-developers] 10.2 and merges (e.g. TokuDB)
Hi there, It seems 10.2.6 is still shipping with TokuDB from PS 5.6.35-80 (Feb 8th 2017). I can't see a jira issue for a 10.2 merge since 10.2.4. Perhaps intentional to help stabilise 10.2 for release? 10.0.30 also shipped with the same Feb version (in March). 10.1.23 however was released in May and still has this version from Feb, which seems unfortunate, but I know it's because it has to flow through 10.0 first. I see 10.0.31 is due to get TokuDB from PS 5.6.36-82 And that should flow into 10.1.24 soon too. However, 10.2.7 isn't due until July, so by then TokuDB version will be 5 months old in 10.2 I'm waiting on a fairly important row count fix that should appear in the next Percona Server release. When it does, if the current merging strategy continues, do I have to first wait for 10.0.32 to get it in late July, then 10.1.26 in August, then 10.2 after that? Or with 10.0, 10.1 and 10.2 all being supported and needing merges, is there a new strategy on the cards to shorten this lag? Thanks! Phil
Hi, Phil! On May 24, Phil Sweeney wrote:
I'm waiting on a fairly important row count fix that should appear in the next Percona Server release.
When it does, if the current merging strategy continues, do I have to first wait for 10.0.32 to get it in late July, then 10.1.26 in August, then 10.2 after that?
This is exactly the strategy we've been using so far, yes.
Or with 10.0, 10.1 and 10.2 all being supported and needing merges, is there a new strategy on the cards to shorten this lag?
This is a good point. Particularly, as 5.5 and 10.0 will be released only quarterly from now on (following MySQL-5.5 release schedule). We'll try a new strategy, https://jira.mariadb.org/browse/MDEV-12881 means that 10.1.25 should have the latest TokuDB (as usual, it's the plan, not a promise; plans may change). Regards, Sergei Chief Architect MariaDB and security@mariadb.org
Hi Sergei, Appreciate you considering other options. Unfortunately in this case it seems Percona did not release a new 5.6 version in time for this 10.1.25 merge. However, interestingly, they did tag a release for 5.7.18-15 in the PerconaFT repository (which is common to both 5.6 and 5.7) in late May, that did include the fix I wanted :) Percona tells me that they will only be doing a 5.6 release once Oracle releases 5.6.37, which could be quite some time (plus the time for Percona to do their thing). Is there potentially a way to deal with this, e.g. accept any tagged release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a different versioning indicator for consistency) I have a feeling that similarly to MariaDB 10.1 only getting quarterly release from now on, Percona 5.6 is probably not going to get as regular attention as 5.7. https://github.com/percona/PerconaFT/tags For example, this year, PerconaFT has had 5 tags for 5.7, but only 3 for 5.6. Thanks, Phil On Wed, May 24, 2017 at 6:14 AM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Phil!
On May 24, Phil Sweeney wrote:
I'm waiting on a fairly important row count fix that should appear in the next Percona Server release.
When it does, if the current merging strategy continues, do I have to first wait for 10.0.32 to get it in late July, then 10.1.26 in August, then 10.2 after that?
This is exactly the strategy we've been using so far, yes.
Or with 10.0, 10.1 and 10.2 all being supported and needing merges, is there a new strategy on the cards to shorten this lag?
This is a good point. Particularly, as 5.5 and 10.0 will be released only quarterly from now on (following MySQL-5.5 release schedule).
We'll try a new strategy, https://jira.mariadb.org/browse/MDEV-12881 means that 10.1.25 should have the latest TokuDB (as usual, it's the plan, not a promise; plans may change).
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
Hi, Phil! On Jun 25, Phil Sweeney wrote:
Hi Sergei,
Appreciate you considering other options. Unfortunately in this case it seems Percona did not release a new 5.6 version in time for this 10.1.25 merge.
However, interestingly, they did tag a release for 5.7.18-15 in the PerconaFT repository (which is common to both 5.6 and 5.7) in late May, that did include the fix I wanted :)
Percona tells me that they will only be doing a 5.6 release once Oracle releases 5.6.37, which could be quite some time (plus the time for Percona to do their thing).
Is there potentially a way to deal with this, e.g. accept any tagged release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a different versioning indicator for consistency)
Yes. Technically, we can merge TokuDB from 5.7 into 10.2. May be we start doing it later, after a first few GA releases of 10.2
I have a feeling that similarly to MariaDB 10.1 only getting quarterly release from now on, Percona 5.6 is probably not going to get as regular attention as 5.7.
MariaDB 10.0 is released quarterly. 10.1 is released twice per quarter. Regards, Sergei Chief Architect MariaDB and security@mariadb.org
Hi Sergei! Le 05/07/2017 à 15:36, Sergei Golubchik a écrit :
Hi, Phil!
On Jun 25, Phil Sweeney wrote:
Hi Sergei,
Appreciate you considering other options. Unfortunately in this case it seems Percona did not release a new 5.6 version in time for this 10.1.25 merge.
However, interestingly, they did tag a release for 5.7.18-15 in the PerconaFT repository (which is common to both 5.6 and 5.7) in late May, that did include the fix I wanted :)
Percona tells me that they will only be doing a 5.6 release once Oracle releases 5.6.37, which could be quite some time (plus the time for Percona to do their thing).
Is there potentially a way to deal with this, e.g. accept any tagged release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a different versioning indicator for consistency) Yes. Technically, we can merge TokuDB from 5.7 into 10.2. May be we start doing it later, after a first few GA releases of 10.2 This fix is really critical for TokuDB users, right now it's almost unusable (I have to fix the server for one of my customer several time a week because the cardinality reaches 0 due to this bug). So the sooner the better :)
Thanks! Jocelyn
Hi, Jocelyn! On Jul 05, jocelyn fournier wrote:
Le 05/07/2017 à 15:36, Sergei Golubchik a écrit :
On Jun 25, Phil Sweeney wrote:
Hi Sergei,
Appreciate you considering other options. Unfortunately in this case it seems Percona did not release a new 5.6 version in time for this 10.1.25 merge.
However, interestingly, they did tag a release for 5.7.18-15 in the PerconaFT repository (which is common to both 5.6 and 5.7) in late May, that did include the fix I wanted :)
Percona tells me that they will only be doing a 5.6 release once Oracle releases 5.6.37, which could be quite some time (plus the time for Percona to do their thing).
Is there potentially a way to deal with this, e.g. accept any tagged release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a different versioning indicator for consistency) Yes. Technically, we can merge TokuDB from 5.7 into 10.2. May be we start doing it later, after a first few GA releases of 10.2 This fix is really critical for TokuDB users, right now it's almost unusable (I have to fix the server for one of my customer several time a week because the cardinality reaches 0 due to this bug). So the sooner the better :)
Understood, thanks. So far it looks like next 10.0 and 10.1 releases will be after Oracle July 2017 CPU, so hopefully Percona will release new 5.6 TokuDB in time for us to merge it. But if not - I'll try to grab it from 5.7, if it'll be usable. Regards, Sergei Chief Architect MariaDB and security@mariadb.org
Hi Sergei, Picking up this thread again. The problem appears to be getting worse. 10.1.35 shipped with old TokuDB despite there being a Percona 5.6 release in May. Given the next 10.0 (10.0.37) is not scheduled for 19 October, are we to assume that the next 10.1 release (10.1.36) will still not get a TokuDB merge? So we're going to have 10.1.36 in September, that will have an 8 month old version of TokuDB, despite new versions of Percona 5.6 being released in May and August. You mentioned in this thread ideas around merging TokuDB straight into 10.1 or 10.2 to avoid the 10.0->10.1->10.2->10.3 lag .. what's the latest thinking on this? Also, will you consider merging from Percona 5.7 instead of 5.6, as it gets much more regular releases. Thanks, Phil On Mon, Jul 10, 2017 at 11:30 PM Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Jocelyn!
On Jul 05, jocelyn fournier wrote:
Le 05/07/2017 ą 15:36, Sergei Golubchik a écrit :
On Jun 25, Phil Sweeney wrote:
Hi Sergei,
Appreciate you considering other options. Unfortunately in this case it seems Percona did not release a new 5.6 version in time for this 10.1.25 merge.
However, interestingly, they did tag a release for 5.7.18-15 in the PerconaFT repository (which is common to both 5.6 and 5.7) in late May, that did include the fix I wanted :)
Percona tells me that they will only be doing a 5.6 release once Oracle releases 5.6.37, which could be quite some time (plus the time for Percona to do their thing).
Is there potentially a way to deal with this, e.g. accept any tagged release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a different versioning indicator for consistency) Yes. Technically, we can merge TokuDB from 5.7 into 10.2. May be we start doing it later, after a first few GA releases of 10.2 This fix is really critical for TokuDB users, right now it's almost unusable (I have to fix the server for one of my customer several time a week because the cardinality reaches 0 due to this bug). So the sooner the better :)
Understood, thanks.
So far it looks like next 10.0 and 10.1 releases will be after Oracle July 2017 CPU, so hopefully Percona will release new 5.6 TokuDB in time for us to merge it. But if not - I'll try to grab it from 5.7, if it'll be usable.
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
Hi, Phil! On Aug 28, Phil Sweeney wrote:
Hi Sergei,
Picking up this thread again. The problem appears to be getting worse. 10.1.35 shipped with old TokuDB despite there being a Percona 5.6 release in May.
Given the next 10.0 (10.0.37) is not scheduled for 19 October, are we to assume that the next 10.1 release (10.1.36) will still not get a TokuDB merge? So we're going to have 10.1.36 in September, that will have an 8 month old version of TokuDB, despite new versions of Percona 5.6 being released in May and August.
I've noted down to include the new TokuDB into 10.1.36 https://jira.mariadb.org/browse/MDEV-17086 So, hopefully, next 10.1 release will have the latest released TokuDB.
Also, will you consider merging from Percona 5.7 instead of 5.6, as it gets much more regular releases.
It's difficult. We've looked at it few times, but it was a lot more work than just a merge, APIs have changed significantly, so it'll take few weeks to integrate :( Regards, Sergei Chief Architect MariaDB and security@mariadb.org
participants (3)
-
jocelyn fournier -
Phil Sweeney -
Sergei Golubchik