New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 9768 link

Starred by 2 users

Issue metadata

Status: Submitted
Owner: ----
Closed: Dec 1
Cc:
Components:



Sign in to add a comment

Make the number of replicas and number of shards configurable

Project Member Reported by david.pu...@gmail.com, Sep 26

Issue description

*****************************************************************
*****                                                       *****
***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!  *****
*****                                                       *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD,  *****
***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.*****
*****                                                       *****
*****   THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS     *****
*****                                                       *****
*****************************************************************

Affected Version: 2.15.x
-as 2.14 no longer bumps its ES version, at least not in a majorly fashion.

What steps will reproduce the problem?

Run against ES 6.4.1

What is the expected output?

No warnings

What do you see instead?

Warning about default number of shards changing in version 7.0.0

Please provide any additional information below.

"the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template"
 
Related to this: we should at some point decide when to cut off with support for ES versions in the 2.14.x series.

We are already at 2.14.13 and will soon release 2.14.14; I don't think we should be doing any more releases on this series except for critical and security issues.

In other words, I don't think we should make effort to support ES 7.0 with 2.14.x, but instead do that on stable-2.15 or master.
Project Member

Comment 2 by marco.mm...@gmail.com, Sep 26

I'd agree with supporting ES 7.x starting with 2.15.y solely (and up), yes.

Assuming that ES 6 will remain stable enough and not go away that much -while 2.14 remains in use for Gerrit production deployments that is. In Ericsson, we are still forecasting 2.15 for later through 2019. And 2.16/master is therefore likely much later for us, around the course of 2020 or so.

Elasticsearch 5 is still well maintained anyway, which is positive also for such considerations.
Project Member

Comment 3 by marco.mm...@gmail.com, Nov 16

Description: Show this description
Project Member

Comment 4 by marco.mm...@gmail.com, Nov 16

Status: Accepted (was: New)
7.0.0-alpha1 is now available on maven-central.
Status: ChangeUnderReview (was: Accepted)
https://gerrit-review.googlesource.com/c/gerrit/+/205981
Project Member

Comment 7 by marco.mm...@gmail.com, Nov 30

Status: Submitted (was: ChangeUnderReview)
Status: Started (was: Submitted)
Summary: Add support for Elasticsearch 7 (was: Elasticsearch: handle default number of shards in version 7.0.0)
Repurposing this issue to be more generally about supporting version 7, and setting back to open state.

Initial support for 7.0.0-alpha1 was already done with https://gerrit-review.googlesource.com/c/gerrit/+/206010

There will be more changes as new alpha releases, and the final release, become available.

Will also need to update the REST client to use the 7.0.0 version.
Status: Submitted (was: Started)
Summary: Make the number of replicas and number of shards comfigurable (was: Add support for Elasticsearch 7)
On second thought, let's keep this issue about the replicas and shards, and open a new issue specifically to add support for v7.

Summary: Make the number of replicas and number of shards configurable (was: Make the number of replicas and number of shards comfigurable)

Sign in to add a comment