KV Testing - When Scan fails, DeleteWhileIterating gets stuck

[itaidavid]

Deadlock due to wrong usage of routines synchronization with channels - both routines report error on the (blocking) error channel, which is never listened, due to the main routine blocked on the sending channels

[itaidavid]

Comment from @arielshaqed:

Please note that this kind of thing will be hard to fix precisely if you allow deletes while iterating. Ideally you could use partitions, and then allow deleting only entire partitions that are completely unused so without concurrent iteration. (Other things can be handled by writing a tombstone).

In really not optimistic about rapid iteration on KVs in the presence of concurrent delete operations.

[github-actions]

This issue is now marked as stale after 90 days of inactivity, and will be closed soon. To keep it, mark it with the "no stale" label.

[github-actions]

Closing this issue because it has been stale for 7 days with no activity.

[arielshaqed]

Is this still open? Sounds like a bug waiting to happen if it is...

[github-actions]

This issue is now marked as stale after 90 days of inactivity, and will be closed soon. To keep it, mark it with the "no stale" label.

[arielshaqed]

This will never go stale, but we might close it if we think about it hard enough and write the explanation here.