[
https://issues.apache.org/jira/browse/STORM-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108336#comment-16108336
]
Jungtaek Lim commented on STORM-2018:
-------------------------------------
[~erikdw], I think we're trying to respect semver, and we missed here.
This patch completely revises Supervisor (say V2) so the diff was quite huge.
Could you file an issue regarding this? I'd be really appreciated if you can
provide a patch and being a tester. (No one claimed this before so that's a
missing point of testing.)
TBH, it would be ideal to support mesos integration officially. Storm
officially supports only standalone, and storm-yarn and storm-mesos are
supported from community which are hard to catch up Storm development. They're
not considered in release verification phase so it's hard to guarantee
compatibility between Storm release and community's efforts.
> 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)
