[Gluster-infra] Opinions on ideal time for gerrit downtime

Nigel Babu nigelb at redhat.com
Wed May 25 11:02:36 UTC 2016

Hello folks,

I'd like to bring down gerrit for 2 hours some time next week to migrate
our database from H2 to PostgreSQL. This will start us on the path to
scaling gerrit better. This migration will also speed up the process of
upgrading gerrit to the latest version and having our install running newer
releases of gerrit quickly.

There is really no good time to bring down an essential service like
gerrit. My proposal is Monday 0230[1] UTC or 1230[2] UTC. I've looked at
our git punchcards and it's a reasonably quiet time to bring down gerrit
for maintenance.

In the meanwhile, I'd appreciate some feedback on review.nigelb.me which is
a snapshot of our gerrit instance from this morning but with the database
powered by postgres. I'd appreciate feedback that the permissions work as
expected and reviewing works as expected. This instance does not replicate
to github, so feel free to push commits to test.

I do not expect this migration to cause any data loss whatsoever (help in
testing review.nigelb.me appreciated!). I'm taking great pains to make sure
the data is transferred over perfectly. In case we run into any problems
during migration, we can fall back to our H2 database pretty instantly.

During the migration window, gerrit will be completely down. I will send in
an email before the start and after the successful completion of the


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20160525/f7a9da92/attachment.html>

More information about the Gluster-infra mailing list