Re: assert(e->mem_status == NOT_IN_MEMORY) versus TCP_MEM_HIT.

fre 2009-09-25 klockan 23:40 +1200 skrev Amos Jeffries:
> This is the current blocker on trunk...
>
> Attempting to swap-in an object which is already in memory and on disk.

Right, there is a timing race uncovered by the swapin changes.

1. store client created and type set to disk client.

[some time may pass]

2. First doCopy call triggers the start of the swapin.

I see two ways of fixing this:

a) Move the swapin start to 1.

b) Make store clients automatically switch from disk to mem type if the
object is found to be already swapped in in doCopy

or alternatively

c) Remove the assert. It's harmless.

Regards
Henrik
Received on Sat Sep 26 2009 - 06:10:05 MDT