Saving pools to persistence table when it's not the LB default

Once the LB has selected pool A, the document is returned from that pool. The client does wait until this is returned and most of the subsequent requests for images, CSS and JS files are honoured correctly (an entry is found in persistence table and the request is directed to the pool that served the parent document).

 

 

However a few of the requests fail to find a persistence entry, get re-sampled and so some end up going to pool B. This pool doesn't know anything about the make-up of the document (it's a different version of the site) and so it actually returns 404s to the client.

 

 

The client definitely waits because often the 2nd and 3rd request will succeed as expected. But then the 4th might fail and find nothing. And the 5th will work ... a mystery. I sometimes find that the persistence table ends up with 2 entries for the same key but different pool values. Shouldn't it only store 1 value per key?