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

Upgrade from Elasticsearch 1.1.2 to 1.5.2

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 7.2
    • Fix Version/s: 7.3
    • Component/s: Core VCS, Elasticsearch
    • Tags:
    • Upgrade notes:
      Hide

      Upgrading Elasticsearch cluster to the latest 1.5.x is not mandatory but advised (1.1.x is still supported).

      Show
      Upgrading Elasticsearch cluster to the latest 1.5.x is not mandatory but advised (1.1.x is still supported).
    • Sprint:
      Sprint RepoTeam 5.9.5-2
    • Epic Link:

      Description

      Upgrading to latest ES 1.5.2 means:

      • upgrade lucene from 4.7.2 to 4.10.4
      • upgrade the nuxeo-core-storage-sql-extension to make h2 uses lucene 4.10.4 (nothing to change on h2database itself)
      • upgrade groovy-all from 1.5.7 to 2.4.0

      Also since datasource are managed by Nuxeo we can move the h2 jdbc driver, elasticsearch, groovy-all and nuxeo-core-storage-sql-extension
      from tomcat/lib to tomcat/nxserver/lib
      The jdbc driver must be deregstered on shutdown.

      Note that the new lucene version does not remove anymore the write.lock files (change since lucene 4.8.0).
      So the Nuxeo launcher should not warn anymore about existing write.lock on startup.

      There should be no problem about ES versions compatibility on the server side. Unit test are fine using Nuxeo (ES 1.5.2) against an ES cluster 1.1.2

      Note that this upgrade is only for the master branch (7.3) changing the library layout does not looks like a good idea for a 6.0 HF.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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