
We now loop over all IndexDefinitions and support online reindexing for each of them independently. They share the single configured batch indexing threadpool, so running an arbitrary (small) number of them shouldn't affect performance more than running one of them. The markReady implementation still does not correctly respect multiple indexes; this obviously needs to be fixed before adding any new index types. Change-Id: Id6c58a595086e7dc22cbc7302169d96c4ccf1aa4
37 lines
1.0 KiB
Plaintext
37 lines
1.0 KiB
Plaintext
= gerrit index start
|
|
|
|
== NAME
|
|
gerrit index start - Start the online indexer
|
|
|
|
== SYNOPSIS
|
|
--
|
|
'ssh' -p @SSH_PORT@ @SSH_HOST@ 'gerrit index start <index>'
|
|
--
|
|
|
|
== DESCRIPTION
|
|
Gerrit supports online index schema upgrades. When starting Gerrit for the first
|
|
time after an upgrade that requires an index schema upgrade, the online indexer
|
|
will be started. If the schema upgrade is a success, the new index will be
|
|
activated and if it fails, a statement in the logs will be printed with the
|
|
number of successfully/failed indexed changes.
|
|
|
|
This command allows restarting the online indexer without having to restart
|
|
Gerrit. This command will not start the indexer if it is already running or if
|
|
the active index is the latest.
|
|
|
|
The <index> argument controls which secondary index is started. Currently, the
|
|
only supported value is "changes".
|
|
|
|
== ACCESS
|
|
Caller must be a member of the privileged 'Administrators' group.
|
|
|
|
== SCRIPTING
|
|
This command is intended to be used in scripts.
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|
|
|
|
SEARCHBOX
|
|
---------
|