Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-19121

Improve default Elasticsearch audit index settings

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 7.10, 8.1
    • Fix Version/s: 7.10-HF07, 8.2
    • Component/s: Audit, Elasticsearch

      Description

      The contribution elasticsearch-audit-index-config.xml.nxftl does not provide a settings section to set the number of shards and replicas of the audit index.

      The default setting is taken from the embedded mode (1shard no replica).

      This should be changed to use the same replicas and shards than the document index.

      To change the number of replicas to 1 for an existing audit index you can use this:

      curl -X PUT localhost:9200/nuxeo-audit/_settings -d '{"index" : {"number_of_replicas" : 1 }}'
      

      Changing the number of shard require to create another index with the proper number of shard and migrade the docs from one index to the new one.
      See the https://doc.nuxeo.com/display/ADMINDOC/Elasticsearch+setup#ElasticsearchSetup-UpdatingtheAuditLogsIndexConfiguration documentation.

      Elasticsearch audit index is now configured with the same number of shards and replicas than the repository index.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 hours
                3h

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.