Investigate concurrent timing issue meaning DB is flushed unexpectedly in IT

13502
Reporter: trobertson
Type: Task
Summary: Investigate concurrent timing issue meaning DB is flushed unexpectedly in IT
Priority: Minor
Status: Open
Created: 2013-07-11 12:24:47.329
Updated: 2013-12-12 17:32:45.772
        
Description: This relates to the DatasetIT where the asynchronous solr updater is building solr annotated datasets but getting NULL values for things.

It is now defensively coded to not fail, and I *believe* this is only rooted in the IT, where the DB updater is flushing the DB for the next test method, while there are still pending SOLR updates to happen asynchronously.  Those updates then look up things, which have been flushed, so it gets NotFoundExceptions (because the interceptor stops it returning null).

I don't believe this to be problematic code, but rather a bad test framework timing issue.]]>
    

Author: kbraak@gbif.org
Comment: Tim, I don't remember ever seeing this issue. Is this the problem that only you and Markus saw, because you are on SSDs?
Created: 2013-12-12 14:21:29.463
Updated: 2013-12-12 14:21:29.463