Author glangford
Recipients Sebastian.Kreft.Deezer, bquinlan, glangford, mark.dickinson, pitrou, python-dev, sbt, tim.peters
Date 2014-06-16.12:00:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402920052.62.0.050743070385.issue20319@psf.upfronthosting.co.za>
In-reply-to
Content
> Any ideas how to debug this further?

Wherever the cause of the problem might live, and to either work around it or gain additional information, here is one idea to consider.

Do you need to submit your Futures just two at a time, and tightly loop every 15s? Why not submit a block of a larger number and wait for the block with as_completed(), logging for each completion. Then submit another block when they are all done. To control how many run at one time, create the Executor with max_workers=2 for example. (I had an app that ran > 1,000 futures in this way, which worked fine). 

In general I suggest to only timeout when there is really a problem, not as an expected event.
History
Date User Action Args
2014-06-16 12:00:52glangfordsetrecipients: + glangford, tim.peters, bquinlan, mark.dickinson, pitrou, python-dev, sbt, Sebastian.Kreft.Deezer
2014-06-16 12:00:52glangfordsetmessageid: <1402920052.62.0.050743070385.issue20319@psf.upfronthosting.co.za>
2014-06-16 12:00:52glangfordlinkissue20319 messages
2014-06-16 12:00:52glangfordcreate