[I] [STORM-17] Spouts should be their own ackers (storm)

["jira-importer (via GitHub)" <gi...@apache.org>]

jira-importer opened a new issue, #3859:
URL: https://github.com/apache/storm/issues/3859

   <p>This would create the following improvements:</p>
   
   <p><a href="https://github.com/nathanmarz/storm/issues/282" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/nathanmarz/storm/issues/282</a></p>
   
   <p>1) Operational: no more need to specify the number of ackers<br/>
   2) More accurate tuple tree tracking: When this is done, spouts can generate the tuple ids and guarantee that they're unique by checking if it already exists already. With the current acker approach, the birthday problem takes effect, and occasionally two different spout tuples will have the same id, causing them both to timeout and fail. See this thread for more details: <a href="http://groups.google.com/group/storm-user/browse_frm/thread/f3267a4a605757e9" class="external-link" target="_blank" rel="nofollow noopener">http://groups.google.com/group/storm-user/browse_frm/thread/f3267a4a605757e9</a><br/>
   3) Better performance: No need for the ack init message from spout -> acker, and no need for ack/fail message from acker -> spout</p>
   
   ---
   <details><summary><i>Originally reported by <a title="James Xu" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=xumingming">xumingming</a>, imported from: <a href="https://issues.apache.org/jira/browse/STORM-17" target="_blank">Spouts should be their own ackers</a></i></summary>
   <i><ul>
   <li><b>status</b>: Closed
   <li><b>priority</b>: Major
   <li><b>resolution</b>: Abandoned
   <li><b>resolved</b>: 2024-07-02T10:54:55+01:00
   <li><b>imported</b>: 2025-01-24
   </ul></i>
   </details>


-- 
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.

To unsubscribe, e-mail: dev-unsubscribe@storm.apache.org.apache.org

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

Re: [I] [STORM-17] Spouts should be their own ackers (storm)

["jira-importer (via GitHub)" <gi...@apache.org>]

jira-importer commented on issue #3859:
URL: https://github.com/apache/storm/issues/3859#issuecomment-2612401376

   <i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rzo1">rzo1</a>:</i>
   <p>We are in the process of migrating our issue tracking system to GitHub issues. This issue has been stale for the last 5 years, and STORM has evolved with many dependency updates since this issue was last updated.</p>
   
   <p>If the issue persists in the latest version of Storm, please feel free to reopen it or provide new context. Thank you very much!</p>


-- 
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.

To unsubscribe, e-mail: dev-unsubscribe@storm.apache.org

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