Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !107

Merged
Created Oct 20, 2016 by Nicolas Wavrant@NicolasMaintainer

Resilency export happen once a day, at a fixed but random time

  • Overview 2
  • Commits 6
  • Changes 14

Before, exporting was happening after a random time between midnight and 6am. This is a bad way to do, because backup may not happen every day exactly. From now, the time of backup is defined randomly thanks to the dcron recipe, but won't change once fixed. Still, it may create some delay during the import, but it's far better than before. Also, if a user defines a custom cron frequency, it will overwrite the default one set by the recipe on 1st run. Finally, a migration code has been embeeded, to migrate all the instances already deployed to a random time in the day, instead of keeping them all running at midnight.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: nicolas-resilient
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7