Jump to: navigation, search
Line 8: Line 8:
 
** <tt>bootstrap.memory_lock: true</tt>
 
** <tt>bootstrap.memory_lock: true</tt>
 
** <tt>thread_pool.write.queue_size: -1</tt>
 
** <tt>thread_pool.write.queue_size: -1</tt>
 
<font color="#B24DE7">'''Olena's Notes:'''
 
 
* 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?
 
 
* So, we do not need to say that the 'elasticsearch.connection.endpoints7x' option should replace the previously used 'elasticsearch.connection.endpoints' option, right?
 
 
* Also, depending on recommendations from Valentyn Martyniuk, we might need to have the following paragraph:
 
</font>
 
  
 
{{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}}
 
{{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}}
  
 
[[Category:V:HTCC:9.0.0DRAFT]]
 
[[Category:V:HTCC:9.0.0DRAFT]]

Revision as of 18:52, December 11, 2020

Upgrading Elasticsearch

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

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.
Comments or questions about this documentation? Contact us for support!