[I] [STORM-26] Bound serialization buffers (storm)

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

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

   <p><a href="https://github.com/nathanmarz/storm/issues/468" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/nathanmarz/storm/issues/468</a></p>
   
   <p>Storm's serialization buffers currently expand to the size of the largest record seen. We've seen cases where unexpected or corrupt records can cause the serialization buffer to grow extremely large (like to size of heap), even though all valid records never come close to this size. This causes strange perf issues that are hard to debug. Storm should bound the size of the serialization buffer, and handle records larger than that with a special, temporary buffer.</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-26" target="_blank">Bound serialization buffers</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:29+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-26] Bound serialization buffers (storm)

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

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

   <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