Doesn't seem like there's any opposition to this. I think we can go ahead and merge https://github.com/apache/storm/pull/2807 in the next day or two.
Den man. 20. aug. 2018 kl. 06.49 skrev Jungtaek Lim <[email protected]>: > For Storm 2.0 I'm OK to drop supporting Ganglia reporter as same as why we > removed storm-druid in Storm 2.0. > > When we drop supporting Ganglia reporter in 1.x it would be backward > incompatible. We just introduced Metrics V2 in Storm 1.2 and I guess few > people use Ganglia reporter, so I feel even OK to drop supporting for 1.x, > but just want to be sure it has no outstanding impact. > > 2018년 8월 18일 (토) 오후 9:37, Stig Rohde Døssing <[email protected]>님이 > 작성: > >> Hi, >> >> The metrics v2 system contains a Ganglia reporter based on Dropwizard >> Metrics' metrics-ganglia module. One of the dependencies of this module is >> licensed under LGPL. In order to avoid including LGPL software in our >> releases, we would have to exclude this module and ask users to manually >> install the relevant jars. >> >> Dropwizard Metrics has dropped support for metrics-ganglia due to the >> license on the LGPL dependency >> https://github.com/dropwizard/metrics/issues/1319. We won't be able to >> upgrade to Metrics version 4+ unless we remove the metrics-ganglia >> dependency. >> >> I'd like to know whether anyone is not okay with removing the Ganglia >> reporter from master and deprecating it in 1.x? If we want to keep Ganglia >> reporting, we should try to find an alternative to metrics-ganglia so we >> don't get stuck on a specific Metrics version. >> >
