prevent ongoing migration locks from accumulating over time #65

New issue

Open

opened 2020-08-17 12:00:45 +02:00 by schmittlauch · 0 comments

schmittlauch commented

2020-08-17 12:00:45 +02:00

Owner

With the approach introduced in 414564705a and following commits, each incoming data migration creates a new MVar lock under the key of a provided source ID. If this lock is never collected, these locks will accumulate, the parent map will grow and the runtime list of threads to wake up also grows.

Possible approach: add timestamp to MVar lock entry, periodically purge old logs and wake up waiting threads.

Could be solved together with #64

With the approach introduced in 414564705a9bb8fb2f1f81938e7f607b4010e78a and following commits, each incoming data migration creates a new MVar lock under the key of a provided source ID. If this lock is never collected, these locks will accumulate, the parent map will grow and the runtime list of threads to wake up also grows. Possible approach: add timestamp to MVar lock entry, periodically purge old logs and wake up waiting threads. Could be solved together with #64