Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade/Installation takes long for large databases #800

Open
patrickatamaniuk opened this issue Jan 21, 2013 · 2 comments
Open

Upgrade/Installation takes long for large databases #800

patrickatamaniuk opened this issue Jan 21, 2013 · 2 comments
Labels
feedback-required internal

Comments

@patrickatamaniuk
Copy link
Contributor

platform: 2.0.4, 2.1.6, 2.2.1 # supported: 2.2.4, 2.3.2
backlogs: 0.9.35 # supported: 1.0.5
ruby: 1.9.3, 1.8.7 # supported: 1.9.3, 2.0.0

Upgrades from 0.9.26 and prior as well as installing backlogs on existing databases can take quite long.
DB with more than 50.000 issues takes more than 3 days.

Workaround: If historic burndown graphs are not relevant, perform the installation/upgrade with the environment variable
rbl_migration_ignore_historic_history=yes
@patrickatamaniuk
Copy link
Contributor Author

This should be noted in the installation instructions?

Ideas:
Maybe the rebuild process can be optimized? only upgrade stories/tasks if bl is configured? Restrict upgrade to bl-relevant tracker types?
Evaluate, if the rebuild rake task can run concurrently to an online production system (using ionice and stuff)

@patrickatamaniuk
Copy link
Contributor Author

possible solution at #806

@waleedjaffar waleedjaffar mentioned this issue Dec 13, 2013
Closed
@jdpf jdpf mentioned this issue Aug 16, 2014
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feedback-required internal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@patrickatamaniuk