Elasticsearch version upgrade

Current Version

• Elastic Server: 6.8.1
• Elastic Client version(OSDU Indexer service): 6.6.1

Proposed Version upgrade

• Elastic Server: 7
• Elastic Client version(OSDU Indexer service): 7

we need to upgrade the client and elastic server version, this would require the following changes...

• Update the Indexer service, code change + lib version upgrade.
• Upgraded Elastic server in all clouds(AWS, Azure, Google, and IBM..etc).

added 1 deleted label

changed the description

changed title from Elastic version upgrade to Elasticsearch version upgrade

@ethiraj would the plan be to move to the latest minor in the 7.x series? As that stands today it would be 7.6.2. Or would something else be considered?

@alex.close we haven't decided on the exact version but it would be helpful to get your input.

added 1 deleted label

@ethiraj For production I would recommend the latest patch for the previous minor at the time of upgrade

@ethiraj I am happy to help if this needs to be prioritized. Do we know which core code changes (indexer) are required? Can we do a quick walkthrough?

added to epic &7 (closed)

mentioned in issue search-service#3 (closed)

Thanks Dania and Alex, As @alex.close mentioned if there are no breaking changes I don't see why we can't upgrade. I will set up a call to discuss the details.

Thanks @ethiraj, please follow the LADR process so we can capture and communicate the decision that comes out of the meeting. We need to (re)inject more discipline now that we have a broader community.

The decision should be captured as described in

https://community.opengroup.org/osdu/platform/system/home/-/wikis/Governance#documentation

removed 1 deleted label

added 1 deleted label

Is this a critical path item?

added 1 deleted label

added R3 Development label

Upgrading to Elastic 7.8 is agreed to be the target for M3 for all CSPs. @osdu/platform/roles/core-contributors

added KBIn Progress M3 labels and removed 1 deleted label

assigned to @Dmitriy_Rudko

EPAM team will do initial analysis before upgrading to assess code changes. @Dmitriy_Rudko

The intent is for this upgrade to be in scope for M3, is that correct? Just want to make sure because I think we all need to upgrade at the same time or the test cases may give bad results.

@Nieten Per my notes from Nov 17th PMC weekly meeting, this is targeted as part of M3 by both AWS and Azure

Sounds good.

moved to home#67 (closed)

mentioned in merge request !601 (merged)