Database maintenance runtimes increased in recent patch?

[Mads]

Hi all,

I recently lost my database and had to reload my lifetime hands. Abit over 2 mill hands. I did my reload in two parts. First part i reloaded before the most recent patch (before 4.17.6) and i didnt experience any issues with the runtime of the database maintenance. However in reloading part 2 my database maintenance has been running for more than 24 hours. (Pt4 is not frozen, it is simply running.)

I am not sure how to debug this and I am reluctant to stop the database maintenance as I know this destroys the database.

In reloading the 2nd part I
1) interrupted the tournament detection/summaries. (Done before with no issues)
2) accidentally reloaded 800k hands i had already loaded (loading duplicate hands also didnt generate any issues in the past)

Can either of these two points affect the runtime of the database maintenance? I know this seems unlikely but these points and upgrading to 4.17.6 is the only thing that is different between the two loads that I did.

I talked with a guy in my poker network and he is also experiencing increased database maintenance runtimes. He is using sql 9.6 whilst I am using sql 10 - hence my thought that the increased database
maintenance runtimes could be related to the most recent patch .

Is it somehow possible to see how many operations are left of
the database maintenance (i.e a progress bar of sorts)?

Or is it possible to restart the maintenance somehow without destroying my database?

Thank you for taking the time to read.

Kind regards,

Mads

[Flag_Hippo]

In reloading the 2nd part I
1) interrupted the tournament detection/summaries. (Done before with no issues)
2) accidentally reloaded 800k hands i had already loaded (loading duplicate hands also didnt generate any issues in the past)

Can either of these two points affect the runtime of the database maintenance?

Not as far as I am aware.

Is it somehow possible to see how many operations are left of the database maintenance (i.e a progress bar of sorts)?

No but there is a bug where sometimes the green bars animation does not stop even when the maintenance has been completed. If that's the case you can check the 'View Import Status' tab and see if the last line there says it has completed.

Or is it possible to restart the maintenance somehow without destroying my database?

It doesn't destroy the database but if maintenance in progress is terminated it can cause the database to perform poorly until it's been run again. The maintenance can be started manually via 'Database -> Database Management -> Housekeeping' and running the following in this order:

1. Reindex
2. Cluster
3. Vacuum/Analyze

If you need further assistance you can report your issue via a Support Ticket.