editVersion mismatch in RecordOutputBlobPath about cross-media-measurement HOT 4 CLOSED

A worker means a pod of the mill.

Oh, if this log is from the integrationTest, then it is not due to a mill losing its claim to a computation, since we only have 1 mill in each inProcessDuchy.

Other scenario that can cause this error is in the AsyncComputationControlService, where the non-aggregators send their initial sketches to the aggregator at the same time, handlerA reads the token and then handlerB read the same token, handlerA then writes the path and causes the updateTime to change, when handlerB tries to write, it would fail.

There aren't many cases in which the updateTime of the computation can change during someone else is trying to update it.

from cross-media-measurement.

This might not be a bug.

By design, the worker who owns the computation can update it only if the computation hasn't been modified by someone else.

For example, if the worker's lock on this computation expires, the computation could be claimed by another worker and gets updated, or maybe the computation is marked FAILED by the herald. Once a computation is updated by someone else, the original worker who claimed it won't be able to update it again.

Such failure is transient and this worker will simply give up current attempt.

from cross-media-measurement.

Disclaimer: this logic is not designed by me.

from cross-media-measurement.

This might not be a bug.

By design, the worker who owns the computation can update it only if the computation hasn't been modified by someone else.

For example, if the worker's lock on this computation expires, the computation could be claimed by another worker and gets updated, or maybe the computation is marked FAILED by the herald. Once a computation is updated by someone else, the original worker who claimed it won't be able to update it again.

Such failure is transient and this worker will simply give up current attempt.

Thank you Yao for the explanation.
I don't really get "another worker". I guess the Computation we discussed about here is the local Computation, which will only be accessed by the single worker. Do you mean "another thread" of the worker?

from cross-media-measurement.