Ticket #148 (closed enhancement: fixed)

Opened 11 months ago

Last modified 2 months ago

Locking for import_runtime

Reported by: ton Assigned to: somebody
Priority: major Milestone: 2.14.X
Component: Backend Version:
Keywords: Cc:

Description

Need to lock the running of import_runtime during an upgrade.

Upgrade does this:

1 preinstall 1 new files on filesystem 1 postinstall, which includes... 1 upgrading database

If an import_runtime starts when the new files are on, but the db is not changed to new structure, could have errors.

Alternatively, if an import_runtime is running over this period and the database is changed from under it (dropped columns?), then could error there too.

Need to lock over the entire upgrade process. import_runtime can hold back.

Luis suggests: http://www.fatalmind.com/software/hatools/index.html, but I don't think this is suitable because it invokes a command, and we need to cover the install process. Maybe a DB lock is required...

Change History

10/13/08 16:28:01 changed by ton

  • milestone changed from Opsview 2.12.X to 2.14.X.

11/14/08 13:25:32 changed by ton

  • status changed from new to closed.
  • resolution set to fixed.

Done. import_runtime in 2.14.1 will check for an upgrade flag.