[
https://issues.apache.org/jira/browse/STORM-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946669#comment-13946669
]
Robert Joseph Evans commented on STORM-120:
-------------------------------------------
What I am interested in is the full stack trace simply because it can give an
indication of the thread that execution is happening on. In this case we see
that the shuffle code was called form
backtype.storm.task.ShellBolt$1.run(ShellBolt.java:129) which is the base
thread insize teh ShellBolt calling handleEmit. If there is any other type of
stack trace that shows up it could indicate how/where we are having the count
object shared with other threads.
> util/acquire-random-range-id is not thread-safe
> -----------------------------------------------
>
> Key: STORM-120
> URL: https://issues.apache.org/jira/browse/STORM-120
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: James Xu
> Priority: Minor
>
> https://github.com/nathanmarz/storm/issues/724
> Concurrent calls to util/acquire-random-range-id with the same parameters can
> result in an IndexOutOfBoundsException, as an increment in one thread may
> occur after the bounds check in another. The resulting curr value can be >=
> the size of the List state.
> https://github.com/nathanmarz/storm/blob/fc5fbb8b352cf91050cdde4a9f9e77e673ab7f48/storm-core/src/clj/backtype/storm/util.clj#L606
--
This message was sent by Atlassian JIRA
(v6.2#6252)
