diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-20 06:08:32 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-20 06:08:32 +0300 |
commit | 6435f44b720d76c8b19dac713a8c11fcc7a1d2a7 (patch) | |
tree | 1abfd4ec289c3222c059d6c03dc1148131e6d731 /doc/integration | |
parent | 52ac2cacfd048c17cdbe2a190a39d3d4ad945961 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration')
-rw-r--r-- | doc/integration/elasticsearch.md | 9 | ||||
-rw-r--r-- | doc/integration/jenkins.md | 2 |
2 files changed, 5 insertions, 6 deletions
diff --git a/doc/integration/elasticsearch.md b/doc/integration/elasticsearch.md index 44f32343151..25dfc970869 100644 --- a/doc/integration/elasticsearch.md +++ b/doc/integration/elasticsearch.md @@ -25,17 +25,16 @@ special searches: ## Installing Elasticsearch Elasticsearch is _not_ included in the Omnibus packages. You will have to -[install it yourself](https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html "Elasticsearch installation documentation") +[install it yourself](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/install-elasticsearch.html "Elasticsearch 6.8 installation documentation") whether you are using the Omnibus package or installed GitLab from source. Providing detailed information on installing Elasticsearch is out of the scope of this document. NOTE: **Note:** Elasticsearch should be installed on a separate server, whether you install -it yourself or by using the -[Amazon Elasticsearch](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-gsg.html) -service. Running Elasticsearch on the same server as GitLab is not recommended -and it will likely cause performance degradation on the GitLab installation. +it yourself or use a cloud hosted offering like Elastic's [Elasticsearch Service](https://www.elastic.co/products/elasticsearch/service) (available on AWS, GCP, or Azure) or the +[Amazon Elasticsearch](http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-gsg.html) service. Running Elasticsearch on the same server as GitLab is not recommended +and will likely cause a degradation in GitLab instance performance. NOTE: **Note:** **For a single node Elasticsearch cluster the functional cluster health status will be yellow** (will never be green) because the primary shard is allocated but replicas can not be as there is no other node to which Elasticsearch can assign a replica. diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md index fe607b2afdf..9f3a52cf4ef 100644 --- a/doc/integration/jenkins.md +++ b/doc/integration/jenkins.md @@ -138,7 +138,7 @@ configured or there was an error reporting the status via the API. ### Merge Request event does not trigger a Jenkins Pipeline -Check the `/var/log/gitlab/gitlab-rails/production.log` file for messages like: +Check [service hook logs](../user/project/integrations/project_services.md#troubleshooting-project-services) for request failures or check the `/var/log/gitlab/gitlab-rails/production.log` file for messages like: ```plaintext WebHook Error => Net::ReadTimeout |