Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
cc1d99ef
Commit
cc1d99ef
authored
Sep 15, 2017
by
Nick Thomas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix / add instructions for installations from source to elasticsearch docs
parent
9d7d845a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
1 deletion
+15
-1
doc/integration/elasticsearch.md
doc/integration/elasticsearch.md
+15
-1
No files found.
doc/integration/elasticsearch.md
View file @
cc1d99ef
...
@@ -83,7 +83,7 @@ Then enable Elasticsearch indexing and run repository indexing tasks:
...
@@ -83,7 +83,7 @@ Then enable Elasticsearch indexing and run repository indexing tasks:
sudo gitlab-rake gitlab:elastic:index
sudo gitlab-rake gitlab:elastic:index
# Installations from source
# Installations from source
bundle exec rake gitlab:elastic:index
bundle exec rake gitlab:elastic:index
RAILS_ENV=production
```
```
Enable Elasticsearch search.
Enable Elasticsearch search.
...
@@ -160,16 +160,26 @@ If you want to run several tasks in parallel (probably in separate terminal
...
@@ -160,16 +160,26 @@ If you want to run several tasks in parallel (probably in separate terminal
windows) you can provide the
`ID_FROM`
and
`ID_TO`
parameters:
windows) you can provide the
`ID_FROM`
and
`ID_TO`
parameters:
```
```
# Omnibus installations
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=1001 ID_TO=2000
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=1001 ID_TO=2000
# Installations from source
bundle exec rake gitlab:elastic:index_repositories ID_FROM=1001 ID_TO=2000 RAILS_ENV=production
```
```
Where
`ID_FROM`
and
`ID_TO`
are project IDs. Both parameters are optional.
Where
`ID_FROM`
and
`ID_TO`
are project IDs. Both parameters are optional.
As an example, if you have 3,000 repositories and you want to run three separate indexing tasks, you might run:
As an example, if you have 3,000 repositories and you want to run three separate indexing tasks, you might run:
```
```
# Omnibus installations
sudo gitlab-rake gitlab:elastic:index_repositories ID_TO=1000
sudo gitlab-rake gitlab:elastic:index_repositories ID_TO=1000
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=1001 ID_TO=2000
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=1001 ID_TO=2000
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=2001
sudo gitlab-rake gitlab:elastic:index_repositories ID_FROM=2001
# Installations from source
bundle exec rake gitlab:elastic:index_repositories RAILS_ENV=production ID_TO=1000
bundle exec rake gitlab:elastic:index_repositories RAILS_ENV=production ID_FROM=1001 ID_TO=2000
bundle exec rake gitlab:elastic:index_repositories RAILS_ENV=production ID_FROM=2001
```
```
Sometimes your repository index process
`gitlab:elastic:index_repositories`
or
Sometimes your repository index process
`gitlab:elastic:index_repositories`
or
...
@@ -183,7 +193,11 @@ it will check every project repository again to make sure that every commit in
...
@@ -183,7 +193,11 @@ it will check every project repository again to make sure that every commit in
that repository is indexed, it can be useful in case if your index is outdated:
that repository is indexed, it can be useful in case if your index is outdated:
```
```
# Omnibus installations
sudo gitlab-rake gitlab:elastic:index_repositories UPDATE_INDEX=true ID_TO=1000
sudo gitlab-rake gitlab:elastic:index_repositories UPDATE_INDEX=true ID_TO=1000
# Installations from source
bundle exec rake gitlab:elastic:index_repositories UPDATE_INDEX=true ID_TO=1000 RAILS_ENV=production
```
```
You can also use the
`gitlab:elastic:clear_index_status`
Rake task to force the
You can also use the
`gitlab:elastic:clear_index_status`
Rake task to force the
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment