Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Configure the Elasticsearch Properties File

Configure the Elasticsearch Properties File

Informatica provides a sample Elasticsearch properties file. To configure Elasticsearch, edit the properties file.
  1. Find the
    elasticsearch.yml
    file in the following directory:
    <elasticsearch installation directory>/config
  2. Use a text editor to open the file, and edit the following properties:
    Property
    Description
    bootstrap.memory_lock
    Sets up memory locking. To prevent any Elasticsearch memory from being swapped out, set to
    true
    . Default is
    true
    .
    cluster.name
    Specify a unique name for the Elasticsearch cluster. If you have multiple clusters, ensure that the name of each cluster is unique. If a cluster has multiple nodes, ensure that on each node of the cluster, the same cluster name is specified.
    discovery.zen.minimum_master_nodes
    Required for a multi-node cluster to prevent data loss and maintain cluster stability. Set to the following value:
    (number of master-eligible nodes / 2) + 1
    For example, if a cluster has three nodes, all of which are master-eligible nodes and can contain data, then set the property to
    (3 / 2) + 1
    , which is rounded to
    2
    .
    discovery.zen.ping.unicast.hosts
    Required for a multi-node cluster. This property is used to specify the discovery setting, which is a list of IP addresses and transport ports of the nodes in the cluster. Use the following format to set the property:
    ["host1:port1","host2:port2","host3:port3"]
    http.port
    Port for the HTTP requests. Default is
    9200
    .
    network.host
    The IP address of the host to use as the bind address.
    node.data
    Enables a node as a data node that performs data related operations, such as CRUD and search. Default is
    true
    .
    node.ingest
    Enables a node as an ingest node that transforms and enriches the data before indexing. Default is
    true
    .
    node.master
    Enables a node as a master node that controls the cluster. If a cluster has multiple nodes, enable at least one of the nodes as a master node. For high availability, set multiple nodes as master nodes. Default is
    true
    .
    node.name
    Specify a unique name for the node.
    path.data
    Path to the directory where you want to store the data. You can configure multiple data directories. For more information about configuring multiple data directories, see the Elasticsearch documentation.
    path.logs
    Path to the log files.
    transport.tcp.port
    The TCP bind port. Default is
    9300
    .
  3. Save the properties file with the same name,
    elasticsearch.yml
    .

0 COMMENTS

We’d like to hear from you!