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

Rick Kellogg updated STORM-481:
-------------------------------
    Component/s: storm-core

> A specific trident topology pattern causes batches to never complete
> --------------------------------------------------------------------
>
>                 Key: STORM-481
>                 URL: https://issues.apache.org/jira/browse/STORM-481
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.9.2-incubating
>            Reporter: Simon Cooper
>            Priority: Critical
>         Attachments: ParallelismTest.java
>
>
> We've discovered that a very specific pattern of partitioning and state 
> persists (that we happen to use) causes a trident topology to never commit 
> batches.
> We've boiled the pattern we use down to this:
> {code}
>         /->Op->\     /->Op->\
> Spout ->-------->->->-------->-x-> Persist
>                    \-> Persist
> {code}
> If there is a {{partitionBy}} at x, then the batches never complete. If the 
> partitioning is not there, then the topology works fine.
> This is reproduced by the attached java testcase. The test will hang 
> (FeederBatchSpout hangs on acquiring a semaphore) if {{failTest}} is true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to