Network Rendering, Stuck Slave Bypass

[Ruckus]

Network Rendering is working fairly well for us.  We get out a lot more work when we are not waiting for our local machines to render.  Occasionally we are experiencing issues where one Slave gets "stuck.

[Ruckus]

(the post above lost most of my text)

When this occurs it can have a devastating affect on that evenings renderings.  Imagine it getting stuck on the second out 40 render jobs in the queue.  So I consider this to be a high priority.

The stuck Slave could be an issue with the slave process, but it could also have a hundred other causes, so I'm not ready to declare that to be a bug.  No matter what causes the Slave to get stuck, I think the Master process can work around it.

If the Master were to track when a tile was sent out in addition to Slave machine, it could then drop that tile after some user specified amount of time (I would choose a half hour).  It might also be a good idea to drop that slave machine entirely, setting its status to deactivated.

[KeyShot]

The latest network rendering update should address this issue.

[DonChunior]

The latest network rendering update should address this issue.

Please provide a download link to the latest release!

How exactely has this issue been resolved?