Actor invocations should clean up after themselves

[deardooley]

Currently when invoking actors repeatedly, the completed containers are left on the execution host. This creates a heck of a stockpile of containers and disk. Having them cleaned up after completion would help the system stay up longer, achieve better throughput, and handle requests for larger containers more promptly.

[joestubbs]

Yes, this is actually fixed in the current version but not deployed to staging yet.

[deardooley]

How is it configured? I’m running from the repo.

—
Rion

On Nov 8, 2015, at 7:30 AM, Joe Stubbs notifications@github.com wrote:

Yes, this is actually fixed in the current version but not deployed to staging yet.

—
Reply to this email directly or view it on GitHub #12 (comment).

[joestubbs]

Hmm, there's no configuration needed. You are seeing actor containers pile up? If so, that's a bug. The commit was from October: 61407c8

[joestubbs]

Pushed a fix. Docker 1.9 broke the stats API since there are multiple networks now, a network must be selected. Since stats collection happens before removal, it was breaking container removal as well. Two of the automated tests are still failing, so I am continuing to look, but manual testing appears to be working.

[joestubbs]

Test are now passing and staging has been updated. Closing out.