Pipelet

My view is that this is more than a bug. We need to rethink the scheduler worker communication to handle such situations as :
- The scheduler got killed or lost connection > the workers should wait some configurable time for him to come back before dying silently
One worker got killed or lost connection -> the scheduler should be able to detect this after a while and resubmit its job
I decrease the priority for next release.