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

Support multiple data paths #11

Closed
danielmitterdorfer opened this issue Dec 11, 2015 · 2 comments
Closed

Support multiple data paths #11

danielmitterdorfer opened this issue Dec 11, 2015 · 2 comments
Labels
enhancement Improves the status quo
Milestone
0.0.2

Comments

@danielmitterdorfer
Copy link
Member

Currently, the benchmark candidate's config option path.data in elasticsearch.yml is allowed to have only one entry. We should allow the user to specify more than one.
@danielmitterdorfer danielmitterdorfer added the enhancement Improves the status quo label Dec 11, 2015
@danielmitterdorfer danielmitterdorfer added this to the 0.0.2 milestone Dec 11, 2015
@danielmitterdorfer
Copy link
Member Author

I thought a bit about this feature and I think we should also keep in mind multi-node setups. So we should have some kind of "node specification" in the future, currently we can only define things on a cluster level with track.CandidateSettings. Apart from other things, the new node specification could contain the setting for path.data.

However, in the first step we could just support single-node setups and put it into track.CandidateSettings directly. wdyt @mikemccand?

@mikemccand
Copy link
Contributor

+1

@danielmitterdorfer danielmitterdorfer self-assigned this Dec 21, 2015
@danielmitterdorfer danielmitterdorfer mentioned this issue Dec 21, 2015
Closed
@danielmitterdorfer danielmitterdorfer removed their assignment Dec 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improves the status quo
Projects
None yet
Milestone
0.0.2
Development

No branches or pull requests
2 participants
@mikemccand @danielmitterdorfer