Planning upgrade from 2.11 to 2.11.4

[David Shrum]

A couple of questions about Gerrit 2.11.4 usage and if rollback from Gerrit 2.11.4 to Gerrit 2.11 would be possible.
We are evaluating upgrading from 2.11 to 2.11.4 as a number of issues have been fixed.

1. If you are using 2.11.4, are there any issues or concerns in upgrading to it from 2.11.
2. Even though there are no DB Schema changes from 2.11 to 2.11.4, would a rollback be possible after 2.11.4 was used for a few days if an issue is identified?  In other words, are there any changes or additions to the data stored in the DB or Gerrit filesystem written by Gerrit 2.11.4 that 2.11 may not recognize if a rollback occurred.

Thanks for any feedback

[Bassem Rabil]

You should be able to rollback safely from 2.11.4 to 2.11 as long as there is no DB schema change. 

[Bassem Rabil]

Also there is no secondary index schema change from 2.11 to 2.11.4, thus both your DB and local secondary index data should be compatible between the 2 releases. 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to a topic in the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/repo-discuss/0LOdYdtW-ow/unsubscribe.
To unsubscribe from this group and all its topics, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Shrum]

Thanks for the information Bassem.  As there is no secondary index schema change from 2.11 to 2.11.4, does that also mean we would not need to do a re-index during the upgrade?

[Bassem Rabil]

Starting 2.11 there is no need to run reindex offline before the upgrade [1], the online reindexer should take care of upgrading the secondary index upon the first launch of the instance whenever there is a change in the secondary index schema version.

In the case of 2.11 to 2.11.4 upgrade, there is no change and thus the online reindexer wouldn't be triggered in this case and no reindexing will be required.

[1] https://gerrit.googlesource.com/gerrit/+/v2.11.4/ReleaseNotes/ReleaseNotes-2.11.txt

[Dirk Heumann]

Hi David,

We still have issues with gerrit 2.11.4 (error within git-upload-pack), one large > 2 GB repo, roughtly 100 users.  We got the system rather stable by running a "git gc" and a "git repack -ab" twice a day, forcing jgit to reinitialize it's memory, but 2.11.x is definitively less stable than the 2.9.x or earlier versions.  A git garbage collection within gerrit was not possible with any version 2.11.x, but after migrating from 2.11 to 2.11.2 we got these damn "git-upload-pack" messages.

You may monitor your error_log for errors more intensely than on previous versions.

Best regards,
Dirk

[David Shrum]

Thanks Dirk. We will keep an eye to see if there is any increase in those specific errors.  As we are running on 2.11, we are already seeing some of those errors, so not sure if going to 2.11.4 will be a regression in that area.  Like you mentioned in another thread, we are also using the default for sshd.tcpKeepAlive which defaults to true.