Skip to content

Conversation

@DaveCTurner
Copy link
Contributor

Today we erroneously look for a node setting called readonly when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes #41009
Relates #26909

Today we erroneously look for a node setting called `readonly` when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes elastic#41009
Relates elastic#26909
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (assuming tests go green), left two suggestions :)

@DaveCTurner DaveCTurner merged commit dc0599a into elastic:master Apr 17, 2019
@DaveCTurner DaveCTurner deleted the 2019-04-16-do-not-recreate-missing-directories-in-readonly-repos branch April 17, 2019 07:34
DaveCTurner added a commit that referenced this pull request Apr 17, 2019
Today we erroneously look for a node setting called `readonly` when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes #41009
Relates #26909
DaveCTurner added a commit that referenced this pull request Apr 17, 2019
Today we erroneously look for a node setting called `readonly` when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes #41009
Relates #26909
DaveCTurner added a commit that referenced this pull request Apr 17, 2019
Today we erroneously look for a node setting called `readonly` when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes #41009
Relates #26909
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
Today we erroneously look for a node setting called `readonly` when deciding
whether or not to create a missing directory in a filesystem repository. This
change fixes this by using the repository setting instead.

Closes elastic#41009
Relates elastic#26909
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Shared filesystem repository does not respect readonly setting

4 participants