[ https://issues.apache.org/jira/browse/STORM-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109127#comment-16109127 ]
Robert Joseph Evans commented on STORM-2018: -------------------------------------------- [~erikdw], Yes we are trying to respect semver. I am sorry it crossed my mind when I was writing the code, but completely spaced it until now (face palm). We should be able to fix these, but it will take a bit of work to be sure that it is all correct. Please file a JIRA against us and assign it to me. I'll do what I can to fix them ASAP. Sorry again. And yes we probably need some step in the release process to look at testing external projects. The ISupervisor interface is really only used by storm mesos right now, as storm-yarn is effectively dead, so it is not always something we pay that much attention to, even though we should. > Simplify Threading Model of the Supervisor > ------------------------------------------ > > Key: STORM-2018 > URL: https://issues.apache.org/jira/browse/STORM-2018 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core > Affects Versions: 1.0.0, 2.0.0 > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > Fix For: 2.0.0, 1.1.0, 1.0.3 > > Attachments: Slot.dot, Slot.svg > > Time Spent: 45h 20m > Remaining Estimate: 0h > > We have been trying to roll out CGROUP enforcement and right now are running > into a number of race conditions in the supervisor. When using CGROUPS the > timing of some operations are different and are exposing issues that we would > not see without this. > In order to make progress with testing/deploying CGROUP and RAS we are going > to try and refactor the supervisor to have a simpler threading model, but > likely with more threads. We will base the code off of the java code > currently in master, and may replace that in the 2.0 release, but plan on > having it be a part of 1.x too, if it truly is more stable. > I will try to keep this JIRA up to date with what we are doing and the > architecture to keep the community informed. We need to move quickly to meet > some of our company goals but will not just shove this in. We welcome any > feedback on the design and code before it goes into the community. -- This message was sent by Atlassian JIRA (v6.4.14#64029)