teun / batchflow Goto Github PK

Sorry if this is an incorrect report, but I've gone through my code so many times I don't know where the issue could be. Every collection I'm using is either concurrent, or modified to support async access. I would expect this error to pop up a little sooner than 10+ hours into the run were it an obvious mistake.

Has this behavior ever been observed before?

System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Collections.Generic.List`1.Enumerator.MoveNext()
   at BatchFlow.TaskNode.Stop()
   at BatchFlow.Flow.Stop()
   at BatchFlow.TaskNode.Worker()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

I was wondering how to increase the default size of streams? Default seems to be 10.

(When working with the function FromAscii)

It would be really nice if BatchFlow could leverage processing power from multiple machines. There are a number of hard nuts to crack here.

#. I think that Redis would be very suitable for the central storage of the queue content. It supports distributed atomic storage and blocking POP calls on queues
#. Some of the patterns that are currently very common for use in BatchFlow will not be (easily) possible in distributed mode. State stored in the closure of lambda expressions will be problematic. Actually, task nodes that are initialized in the current way (using a lambda in the contructor) will not be possible anyway, as they cannot be serialized and deserialized on another machine

TBC