GitHub user hackbert opened a pull request:

    https://github.com/apache/spark/pull/7493

    [SPARK-9094] [PARENT] Increased io.dropwizard.metrics from 3.1.0 to 3.1.2

    We are running Spark 1.4.0 in production and ran into problems because 
after a network hiccup (which happens often in our current environment) no more 
metrics were reported to graphite leaving us blindfolded about the current 
state of our spark applications. [This 
problem](https://github.com/dropwizard/metrics/commit/70559816f1fc3a0a0122b5263d5478ff07396991)
 was fixed in the current version of the metrics library. We run spark with 
this change  in production now and have seen no problems. We also had a look at 
the commit history since 3.1.0 and did not detect any potentially  incompatible 
changes but many fixes which could potentially help other users as well. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/otto-de/spark bump-metrics-lib-version

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/7493.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #7493
    
----
commit 6677565e5c9ded890dc56cb1d476304a763fe25c
Author: Carl Anders Düvel <[email protected]>
Date:   2015-07-18T10:32:51Z

    [SPARK-9094] [PARENT] Increased io.dropwizard.metrics from 3.1.0 to 3.1.2 
in order to get this fix 
https://github.com/dropwizard/metrics/commit/70559816f1fc3a0a0122b5263d5478ff07396991

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to