Yes, that would be good too. 2018-07-29 15:32 GMT+02:00 Jungtaek Lim <kabh...@gmail.com>:
> IMHO I'd take this as a voice for release 1.2.3. We have addressed 21 > issues so far for Storm 1.2.3, so worth to call it for new maintenance > release. > > https://issues.apache.org/jira/projects/STORM/versions/12343340 > > -Jungtaek Lim (HeartSaVioR) > > 2018년 7월 29일 (일) 오후 7:42, Stig Rohde Døssing <s...@apache.org>님이 작성: > >> I'm not aware of a workaround, but why not check out 1.x-branch and build >> storm-kafka-client yourself? You shouldn't need to upgrade the Storm >> cluster to a snapshot to fix this, just replace the storm-kafka-client jar. >> >> 2018-07-26 17:28 GMT+02:00 Mitchell Rathbun (BLOOMBERG/ 731 LEX) < >> mrathb...@bloomberg.net>: >> >>> https://issues.apache.org/jira/browse/STORM-3013 >>> >>> The above JIRA item explains an issue that we see very frequently when >>> shutting down our Storm topology. The listed fix versions are 2.0.0 and >>> 1.2.3, both of which I don't believe have been officially released. Is >>> there a workaround for this issue in the mean time? I don't think it is a >>> critical issue, but it would be nice to not always get these messages in >>> our logs. >>> >> >>
