Gerrit Re-index questions

169 views
Skip to first unread message

adrien...@gmail.com

unread,
Jun 29, 2021, 7:53:07 PM6/29/21
to Repo and Gerrit Discussion
Hi,

We setup a Gerrit HA environment in one Data Center plus one Non-HA Gerrit DR instance on another Data Center.

As we exercised DR failover, we noticed that the Gerrit UI did not showed the commits/changes from the Gerrit HA cluster. 
Note that our DR instance being Non-HA is Cold (stop mode) by default. But it shares the same NFS used by the HA Cluster which hosts the /repos and /share folders.

After we did a re-index in the DR instance which took about 2hrs and 45mins, we were then able to see the changes in the Gerrit UI.

Now we were thinking whether do we really need to do the re-index every time we do a DR failover? 

Or is there a way to configure Gerrit and move the /index folder from the $GERRIT_SITE into the same NFS filesystem (shared by both HA and Non-HA Gerrit)?

Reason we asked is since we are moving away from our current Gerrit production (non-ha), we foresee a data refresh in the First Server of the HA Cluster as part of the cutover and right after the data refresh, we will run a re-index. 
We thought that maybe we and can reuse the same /index folder in the DR instance by taking advantage of the NFS so that in future failover, we do not need to run a re-index again.

Moreover, is there anyone who can enlighten us about the Delta Reindex process? We have never tried it so we are looking how we can do this incremental indexing.

Hope to hear from anyone soon.

Regards,

Adrien

Luca Milanesio

unread,
Jun 29, 2021, 8:01:14 PM6/29/21
to Repo and Gerrit Discussion, Luca Milanesio

On 30 Jun 2021, at 00:53, adrien...@gmail.com <adrien...@gmail.com> wrote:

Hi,

We setup a Gerrit HA environment in one Data Center plus one Non-HA Gerrit DR instance on another Data Center.

As we exercised DR failover, we noticed that the Gerrit UI did not showed the commits/changes from the Gerrit HA cluster. 
Note that our DR instance being Non-HA is Cold (stop mode) by default. But it shares the same NFS used by the HA Cluster which hosts the /repos and /share folders.

After we did a re-index in the DR instance which took about 2hrs and 45mins, we were then able to see the changes in the Gerrit UI.

Now we were thinking whether do we really need to do the re-index every time we do a DR failover? 

You can make a multi-site setup (see [1]) that is exactly designed to manage that configuration.


Or is there a way to configure Gerrit and move the /index folder from the $GERRIT_SITE into the same NFS filesystem (shared by both HA and Non-HA Gerrit)?

Reason we asked is since we are moving away from our current Gerrit production (non-ha), we foresee a data refresh in the First Server of the HA Cluster as part of the cutover and right after the data refresh, we will run a re-index. 
We thought that maybe we and can reuse the same /index folder in the DR instance by taking advantage of the NFS so that in future failover, we do not need to run a re-index again.

Lucene indexes cannot be shared across Gerrit servers.


Moreover, is there anyone who can enlighten us about the Delta Reindex process? We have never tried it so we are looking how we can do this incremental indexing.


Hope to hear from anyone soon.

Regards,

Adrien

--
--
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 the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/43baea20-bde4-4ff9-a09f-ecb2b746c60dn%40googlegroups.com.

Reply all
Reply to author
Forward
0 new messages