Jump to: navigation, search
(GAPI-25163)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=Upgrading Elasticsearch=
 
=Upgrading Elasticsearch=
  
−
Starting with release 9.0.002.{{Editgrn_open}}xx{{Editgrn_close}}, Web Services and Applications support Elasticsearch 7.8. No data migration from the previous version is needed.
+
Starting with release 9.0.002.80, Web Services and Applications require Elasticsearch 7.8. No data migration from the previous version is needed.
  
−
You need to deploy Elasticsearch 7.8 and update the <tt>elasticsearch.yml</tt> file:
+
{{NoteFormat|You need to deploy Elasticsearch 7.8 in parallel with the existing Elasticsearch 6.x and update the <tt>elasticsearch.yml</tt> file.}}
−
* The following options must be set in the <tt>elasticsearch.yml</tt> file on each Elasticsearch node:
 
−
** <tt>action.auto_create_index: false</tt>
 
−
** <tt>bootstrap.memory_lock: true</tt>
 
−
** <tt>thread_pool.write.queue_size: -1</tt>
 
−
* The following options, which were needed for Elasticsearch 6.x, should be removed from the <tt>elasticsearch.yml</tt> file on each Elasticsearch node:
 
−
** <tt>thread_pool.index.queue_size: -1</tt>
 
−
** <tt>thread_pool.bulk.queue_size: -1</tt>
 
  
−
<font color="#B24DE7">'''Olena's Notes:'''
+
The following options must be set in the <tt>elasticsearch.yml</tt> file on each Elasticsearch node:
 +
* <tt>action.auto_create_index: false</tt>
 +
* <tt>bootstrap.memory_lock: true</tt>
 +
* <tt>thread_pool.write.queue_size: -1</tt>
  
−
* The DataCollector Service instance configuration options form the https://intranet.genesys.com/pages/viewpage.action?spaceKey=RP&title=DataCollector+Deployment+Guide are not documented anywhere. This is for internal use only, correct?
+
{{NoteFormat|The <tt>ELASTICSEARCH_ADDR</tt> parameter in the <tt>/opt/genesys/gws/kubernetes/parameters.yaml</tt> file has to point the new Elasticsearch 7.8 installation.|2}}
  
−
* So, we do not need to say that the 'elasticsearch.connection.endpoints7x' option should replace the previously used 'elasticsearch.connection.endpoints' option, right?
+
After a successful upgrade of Web Services and Applications you can remove Elasticsearch 6.x.
−
 
 
−
* Also, depending on recommendations from Valentyn Martyniuk, we might need to have the following paragraph:
 
−
</font>
 
−
 
 
−
{{Chgbar_open}}If you are deploying Elasticsearch 7.8 in parallel with the existing Elasticsearch 6.x, make sure to set the <tt>ELASTICSEARCH_ADDR</tt> parameter in the <tt>/opt/genesys/gws/kubernetes/parameters.yaml</tt> file to your new Elasticsearch 7.8 installation address.{{Chgbar_close}}
 
  
 
[[Category:V:HTCC:9.0.0DRAFT]]
 
[[Category:V:HTCC:9.0.0DRAFT]]

Latest revision as of 17:59, December 14, 2020

Upgrading Elasticsearch

Starting with release 9.0.002.80, Web Services and Applications require Elasticsearch 7.8. No data migration from the previous version is needed.

Important
You need to deploy Elasticsearch 7.8 in parallel with the existing Elasticsearch 6.x and update the elasticsearch.yml file.

The following options must be set in the elasticsearch.yml file on each Elasticsearch node:

  • action.auto_create_index: false
  • bootstrap.memory_lock: true
  • thread_pool.write.queue_size: -1
Tip
The ELASTICSEARCH_ADDR parameter in the /opt/genesys/gws/kubernetes/parameters.yaml file has to point the new Elasticsearch 7.8 installation.

After a successful upgrade of Web Services and Applications you can remove Elasticsearch 6.x.

This page was last edited on December 14, 2020, at 17:59.
Comments or questions about this documentation? Contact us for support!