You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by GitBox <gi...@apache.org> on 2019/10/14 09:05:59 UTC

[GitHub] [hadoop-ozone] elek opened a new pull request #15: HDDS-2296. ozoneperf compose cluster shouln't start freon by default

elek opened a new pull request #15: HDDS-2296. ozoneperf compose cluster shouln't start freon by default
URL: https://github.com/apache/hadoop-ozone/pull/15
 
 
   ## What changes were proposed in this pull request?
   
   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.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-2296
   
   ## How this patch can be tested?
   
   Go to the `compose/ozoneperf` dir and follow the updated README ;-)
   
   (TLDR; start the cluster, wait, start freon with the documented command)

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org