Commit 18771d3f authored by Russell Dickenson's avatar Russell Dickenson

Remove unnecessary note admonitions

parent 626c6ef7
...@@ -66,14 +66,12 @@ source. You must [install it separately](https://www.elastic.co/guide/en/elastic ...@@ -66,14 +66,12 @@ source. You must [install it separately](https://www.elastic.co/guide/en/elastic
Be sure to select your version. Providing detailed information on installing Be sure to select your version. Providing detailed information on installing
Elasticsearch is out of the scope of this document. Elasticsearch is out of the scope of this document.
NOTE: **Note:**
Elasticsearch should be installed on a separate server, whether you install Elasticsearch should be installed on a separate server, whether you install
it yourself or use a cloud hosted offering like Elastic's [Elasticsearch Service](https://www.elastic.co/elasticsearch/service) it yourself or use a cloud hosted offering like Elastic's [Elasticsearch Service](https://www.elastic.co/elasticsearch/service)
(available on AWS, GCP, or Azure) or the [Amazon Elasticsearch](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-gsg.html) (available on AWS, GCP, or Azure) or 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 service. Running Elasticsearch on the same server as GitLab is not recommended
and can cause a degradation in GitLab instance performance. and can cause a degradation in GitLab instance performance.
NOTE: **Note:**
**For a single node Elasticsearch cluster the functional cluster health status **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 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 replicas can not be as there is no other node to which Elasticsearch can assign a
...@@ -164,7 +162,6 @@ may need to set the `production -> elasticsearch -> indexer_path` setting in you ...@@ -164,7 +162,6 @@ may need to set the `production -> elasticsearch -> indexer_path` setting in you
## Enabling Advanced Search ## Enabling Advanced Search
NOTE: **Note:**
For GitLab instances with more than 50GB repository data you can follow the instructions for [Indexing large For GitLab instances with more than 50GB repository data you can follow the instructions for [Indexing large
instances](#indexing-large-instances) below. instances](#indexing-large-instances) below.
...@@ -309,7 +306,6 @@ CAUTION: **Caution:** ...@@ -309,7 +306,6 @@ CAUTION: **Caution:**
It is highly recommended that you take a snapshot of your cluster to ensure It is highly recommended that you take a snapshot of your cluster to ensure
there is a recovery path if anything goes wrong. there is a recovery path if anything goes wrong.
NOTE: **Note:**
Due to a technical limitation, there will be a slight downtime because of the Due to a technical limitation, there will be a slight downtime because of the
fact that we need to reclaim the current `primary` index to be used as the alias. fact that we need to reclaim the current `primary` index to be used as the alias.
...@@ -407,7 +403,6 @@ To trigger the re-index from `primary` index: ...@@ -407,7 +403,6 @@ To trigger the re-index from `primary` index:
Under **Admin Area > Settings > General > Advanced Search > Elasticsearch zero-downtime reindexing**, click on **Trigger cluster reindexing**. Under **Admin Area > Settings > General > Advanced Search > Elasticsearch zero-downtime reindexing**, click on **Trigger cluster reindexing**.
NOTE: **Note:**
Reindexing can be a lengthy process depending on the size of your Elasticsearch cluster. Reindexing can be a lengthy process depending on the size of your Elasticsearch cluster.
CAUTION: **Caution:** CAUTION: **Caution:**
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment