You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Raj Choudhury (JIRA)" <ji...@apache.org> on 2019/08/08 16:22:00 UTC

[jira] [Updated] (STORM-3483) Backpressure turns on after topology is idle for 160 minutes

     [ https://issues.apache.org/jira/browse/STORM-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raj Choudhury updated STORM-3483:
---------------------------------
     Attachment: image-2019-08-08-17-21-18-201.png
                 image-2019-08-08-17-21-50-905.png
    Description: 
Storm version used 1.2.2

While testing a topology we noticed that backpressure was being triggered on an idle topology, without any data going through the system for roughly 160 minutes. However once we starting putting data through the system, backpressure behaved as normal and is off.

We have storm metrics logger to log the disruptor queue sizes, and during this test we can see the receive queue population is 0 when backpressure kicks in. 

 

We confirmed this by turning debug logs on for storm.

!image-2019-08-08-17-21-50-905.png!

 

What a normal system with data going through looks like...

!image-2019-08-08-15-59-25-655.png!

 

In an idle system where backpressure occurs... 

!image-2019-08-08-16-02-09-750.png!

 

  was:
Storm version used 1.2.2

While testing a topology we noticed that backpressure was being triggered on an idle topology, without any data going through the system for roughly 160 minutes. However once we starting putting data through the system, backpressure behaved as normal and is off.

We have storm metrics logger to log the disruptor queue sizes, and during this test we can see the receive queue population is 0 when backpressure kicks in. 

 

We confirmed this by turning debug logs on for storm.

!image-2019-08-08-16-04-45-092.png!

What a normal system with data going through looks like...

!image-2019-08-08-15-59-25-655.png!

 

In an idle system where backpressure occurs... 

!image-2019-08-08-16-02-09-750.png!

 


> Backpressure turns on after topology is idle for 160 minutes
> ------------------------------------------------------------
>
>                 Key: STORM-3483
>                 URL: https://issues.apache.org/jira/browse/STORM-3483
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.2.2
>            Reporter: Raj Choudhury
>            Priority: Minor
>         Attachments: image-2019-08-08-15-23-42-157.png, image-2019-08-08-15-59-25-655.png, image-2019-08-08-16-02-09-750.png, image-2019-08-08-17-21-18-201.png, image-2019-08-08-17-21-50-905.png
>
>
> Storm version used 1.2.2
> While testing a topology we noticed that backpressure was being triggered on an idle topology, without any data going through the system for roughly 160 minutes. However once we starting putting data through the system, backpressure behaved as normal and is off.
> We have storm metrics logger to log the disruptor queue sizes, and during this test we can see the receive queue population is 0 when backpressure kicks in. 
>  
> We confirmed this by turning debug logs on for storm.
> !image-2019-08-08-17-21-50-905.png!
>  
> What a normal system with data going through looks like...
> !image-2019-08-08-15-59-25-655.png!
>  
> In an idle system where backpressure occurs... 
> !image-2019-08-08-16-02-09-750.png!
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)