I'm assuming that the StateManagerprotects itself against race
conditions for the consuming (custom) processor, but I'd like
confirmation on that. Let's say something simple like we get an integer
out of state to which we can add one to get the next (piece of work to
do), then immediately bump and write that value plus 1 for the next
thread to get. In the time it took us to get the value back, bump it by
1, then put it out (I'm assuming Scope.LOCAL), I don't see that the
StateManageris prevented from handing out that same value to another
instance or task of my processor.
How does StateManager Scopeaffect this? (By whether the instance of
state is per host or per cluster?)
How does processor behavior annotation affect this?
How does processor scheduling configuration (concurrent task count)
affect this?
Thanks for any comments.
