Jungtaek Lim resolved STORM-2306.
       Resolution: Fixed
    Fix Version/s: 2.0.0

Marking as resolved since [~revans2] merged this in.

I've reported higher CPU in multiple workers in the patch.
[~roshan_naik] If you can reproduce it, could you please file a follow-up issue 
(with setting priority to blocker) and assign to you? I'll label it as Storm 
2.0.0 epic.

> Redesign Messaging Subsystem and switch to JCTools Queues
> ---------------------------------------------------------
>                 Key: STORM-2306
>                 URL: https://issues.apache.org/jira/browse/STORM-2306
>             Project: Apache Storm
>          Issue Type: Sub-task
>          Components: storm-core
>    Affects Versions: 2.0.0
>            Reporter: Roshan Naik
>            Assignee: Roshan Naik
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>          Time Spent: 60h
>  Remaining Estimate: 0h
> Details in these documents:
> 1) *Redesign of the messaging subsystem*
> https://docs.google.com/document/d/1NK1DJ3aAkta-Im0m-2FObQ4cSRp8xSa301y6zoqcBeE/edit?usp=sharing
> This doc discusses the new design for the messaging system. Plus some of the 
> optimizations being made.
> 2) *Choosing a high performance messaging queue:*
> https://docs.google.com/document/d/1PpQaWVHg06-OqxTzYxQlzg1yEhzA4Y46_NC7HMO6tsI/edit?usp=sharing
> This doc looks into how fast hardware can do inter-thread messaging and why 
> we chose the JCTools queues.
> 3) *Backpressure Model*
> https://docs.google.com/document/d/1Z9pRdI5wtnK-hVwE3Spe6VGCTsz9g8TkgxbTFcbL3jM/edit?usp=sharing
> Describes the Backpressure model integrated into the new messaging subsystem.

This message was sent by Atlassian JIRA

Reply via email to