You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by GitBox <gi...@apache.org> on 2020/09/29 20:26:53 UTC

[GitHub] [storm] Chandan83 opened a new pull request #3338: STORM-3693: Pending tuples expired only once per tick.

Chandan83 opened a new pull request #3338:
URL: https://github.com/apache/storm/pull/3338


   ## What is the purpose of the change
   
   *(To ensure spout pending tuples are expired only once per tick. Otherwise, tuples get expired prematurely when one spout executor has multiple tasks.)*
   
   ## How was the change tested
   
   *(1.  mvn clean install -P '!examples,!externals' 2. Used a dummy topology to test the correct behavior.)*


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [storm] Chandan83 commented on pull request #3338: STORM-3693: Pending tuples expired only once per tick.

Posted by GitBox <gi...@apache.org>.

Chandan83 commented on pull request #3338:
URL: https://github.com/apache/storm/pull/3338#issuecomment-703207390


   @nathanmarz I am wondering if I can do something more to garner some attention to this PR. The fix seems to address a fundamental bug related to tuple expiry. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org