[ 
https://issues.apache.org/jira/browse/HDDS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498650#comment-16498650
 ] 

Anu Engineer commented on HDDS-143:
-----------------------------------

[~elek] This is awesome. Love it. I will commit this shortly, I just ran it on 
my dev box and it amazing to have prometheus running along with ozone even when 
we do dev work.  Two minor comments:
 # On my mac box, I had to execute chmod +x on init.sh and compose-all.sh.
 # Running compose-all.sh did not run "freon". Thought a container called freon 
came up. I had to log into a datanode and run freon by hand to get it working. 
Could be some race condition.
 # Once I ran freon but OM UI and prometheus worked as expected.

> Provide docker compose files to measure performance in a pseudo cluster
> -----------------------------------------------------------------------
>
>                 Key: HDDS-143
>                 URL: https://issues.apache.org/jira/browse/HDDS-143
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-143.002.patch, prometheus_example.png
>
>
> Currently we have one docker-compose file to run local pseudo cluster with 
> Ozone/HDDS. But it's hard to do longer performance tests as we have no 
> metrics collector in the compose files.
> This patch provide a simple solution: it includes a prometheus server and a 
> consul component. With the init script you can download the required java 
> agent: the agent will publish jmx metrics on a prometheus compatible endpoint 
> and register the metrics endpoint in the consul. Prometheus collects the data 
> from the registered endpoints.
> More details about the usage are included in the README.md.
> I run this cluster in my development machine (SSD, 16G ram) with one freon 
> and 3 datanodes. The average rate of key creation was around 180-220 key / 
> seconds.
> The compose file could also help to check the available metrics or compare 
> performance before/after a patch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to