Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix custom data paths to work with security manager #12714

Closed
clintongormley opened this issue Aug 7, 2015 · 0 comments
Closed

Fix custom data paths to work with security manager #12714

clintongormley opened this issue Aug 7, 2015 · 0 comments
Assignees
@dakrone
Labels
blocker >bug v2.0.0-beta1

Comments

@clintongormley
Copy link

Custom data paths in shadow replicas will not work with the security manager today.
@dakrone dakrone mentioned this issue Aug 7, 2015
Merged
dakrone added a commit to dakrone/elasticsearch that referenced this issue Aug 12, 2015
@dakrone
Add path.shared_data
ff5ad39 
This allows `path.shared_data` to be added to the security manager while
still allowing a custom `data_path` for indices using shadow replicas.

For example, configuring `path.shared_data: /tmp/foo`, then created an
index with:

```
POST /myindex
{
  "index": {
    "number_of_shards": 1,
    "number_of_replicas": 1,
    "data_path": "/tmp/foo/bar/baz",
    "shadow_replicas": true
  }
}
```

The index will then reside in `/tmp/foo/bar/baz`.

`path.shared_data` defaults to `null` if not specified.

Resolves elastic#12714
Relates to elastic#11065
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dakrone dakrone

Labels
blocker >bug v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dakrone @clintongormley