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

Set heap dump path #417

Closed
danielmitterdorfer opened this issue Feb 13, 2018 · 0 comments
Closed

Set heap dump path #417

danielmitterdorfer opened this issue Feb 13, 2018 · 0 comments
Labels
:Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch enhancement Improves the status quo
Milestone
0.9.2

Comments

@danielmitterdorfer
Copy link
Member

Currently Rally relies on the default settings of Elasticsearch which enables heap dumps but does not set a path. The JVM will default to the current directory (which is the ES root directory). As it gets wiped by default by Rally after the benchmark we might lose important information.

Hence, we will set a dedicated path for heap dumps next to the Elasticsearch installation directory so heap dumps will be preserved.
@danielmitterdorfer danielmitterdorfer added enhancement Improves the status quo :Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch labels Feb 13, 2018
@danielmitterdorfer danielmitterdorfer added this to the 0.9.2 milestone Feb 13, 2018
danielmitterdorfer added a commit to elastic/rally-teams that referenced this issue Feb 13, 2018
@danielmitterdorfer
Set heap dump path
af3efa1 
Relates elastic/rally#417
danielmitterdorfer added a commit to elastic/rally-teams that referenced this issue Feb 13, 2018
@danielmitterdorfer
Set heap dump path
7859fd9 
Relates elastic/rally#417
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch enhancement Improves the status quo
Projects
None yet
Milestone
0.9.2
Development

No branches or pull requests
1 participant
@danielmitterdorfer