Feature #5432

Database purge

Added by Kalle Kondelin almost 3 years ago. Updated over 2 years ago.

Status:ClosedStart date:2014-10-23
Priority:1Due date:2014-11-07
Assignee:Kalle Kondelin% Done:

100%

Category:DB serverEstimated time:35.00 hours
Target version:1.18.1Spent time:-
Release notes:Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new database.
Tags: db, server, purge
Story points-
Velocity based estimate-
ReleaseSimantics 1.18.1Release relationshipAuto

Description

Summary

Currently database collects history of past operations as journal and change sets. In time this information will take too much space. We need operation that will remove this history data.

Associated revisions

Revision 30539
Added by Kalle Kondelin almost 3 years ago

Fixes #5432. Database purge.

Revision 30697
Added by Kalle Kondelin over 2 years ago

Refs #5432. Database purge.
Purge is now done automatically.
Contains also new delete cluster and list clusters functionality.

History

#1 Updated by Tuukka Lehtonen almost 3 years ago

  • Release set to 16

#2 Updated by Kalle Kondelin almost 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

#3 Updated by Tuukka Lehtonen almost 3 years ago

  • Target version changed from 1.17.1 to 1.18.1

#4 Updated by Kalle Kondelin almost 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

Applied in changeset r30539.

#5 Updated by Kalle Kondelin almost 3 years ago

  • Status changed from Resolved to Feedback
  • Release notes set to Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new workspace.

#6 Updated by Kalle Kondelin almost 3 years ago

  • Release notes changed from Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new workspace. to Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new database.

#7 Updated by Tuukka Lehtonen almost 3 years ago

  • Release changed from 16 to 17

#8 Updated by Tuukka Lehtonen over 2 years ago

  • Tags set to db, server, purge

#9 Updated by Kalle Kondelin over 2 years ago

Reversed the purge logic so that purge is now done by default every time the server is started via user interface. This behavior can be disabled by giving org.simantics.db.procore.ui.skipPurge property the value "true".

Note also that with purge we lose history (change sets), journal and guard files. This means that we also lose (or actually do not handle) the information of accidental client/server process deaths.

This commit also contains delete cluster and list clusters functionality. Sorry about that.

#10 Updated by Tuukka Lehtonen over 2 years ago

  • Status changed from Feedback to Closed

#11 Updated by Tuukka Lehtonen over 2 years ago

  • Release notes changed from Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new database. to Purge operation added to database. Removes old history i.e. change sets from database. Before this the only way to purge old history was to export the database content, create new database and to import the exported content to the new database.

Also available in: Atom PDF