diff options
| author | Pierre Guillot <pierre.guillot@sonarsource.com> | 2019-08-15 10:26:44 +0200 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2019-08-15 20:20:59 +0200 |
| commit | 250d2da7e38b82bc29f70e6f03bae2e80d6808d4 (patch) | |
| tree | f66d7e89366a53ac56a9e5b181f0d6e5566c7f42 | |
| parent | 11231d2eeced80bbc798e4f82f4c7892138675fc (diff) | |
| download | sonarqube-250d2da7e38b82bc29f70e6f03bae2e80d6808d4.tar.gz sonarqube-250d2da7e38b82bc29f70e6f03bae2e80d6808d4.zip | |
DOC fix es version in faq
| -rw-r--r-- | server/sonar-docs/src/pages/faq.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/faq.md b/server/sonar-docs/src/pages/faq.md index 9ee171505fe..3fa570d163d 100644 --- a/server/sonar-docs/src/pages/faq.md +++ b/server/sonar-docs/src/pages/faq.md @@ -20,7 +20,7 @@ This can be automated by using the corresponding Web API: `api/projects/bulk_del Currently, the only way to force a reindex is to: * Stop your server -* Remove the contents of the $SQ_HOME/data/es5 directory +* Remove the contents of the $SQ_HOME/data/es6 directory * Start your server Before doing this, you should be aware first that processes are in place on the SonarQube side that out-of-sync indices are detected and corrected, and second that a full re-index can be quite lengthy depending on the size of your instance. |