[
https://issues.apache.org/jira/browse/HDDS-2296?focusedWorklogId=332984&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-332984
]
ASF GitHub Bot logged work on HDDS-2296:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Oct/19 00:45
Start Date: 24/Oct/19 00:45
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on pull request #15:
HDDS-2296. ozoneperf compose cluster shouln't start freon by default
URL: https://github.com/apache/hadoop-ozone/pull/15
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 332984)
Time Spent: 20m (was: 10m)
> ozoneperf compose cluster shouln't start freon by default
> ---------------------------------------------------------
>
> Key: HDDS-2296
> URL: https://issues.apache.org/jira/browse/HDDS-2296
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: docker
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During the original creation of the compose/ozoneperf we added an example
> freon execution to make it clean how the data can be generated. This freon
> process starts all the time when ozoneperf cluster is started (usually I
> notice it when my CPU starts to use 100% of the available resources).
> Since the creation of this cluster definition we implemented multiple type of
> freon tests and it's hard predict which tests should be executed. I propose
> to remove the default execution of the random key generation but keep the
> opportunity to run any of the tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
