responses inline. > Marking a worker as unschedulable in a persisted manner is non trivial. > We would have to introduce a new internal topic to track this or leverage > something like ZK. I didn't think it was worthwhile for us to add these > new resources / potential dependencies for this feature. That is why I > proposed that leaders track them just in memory and if a leader were to > fail during a drain, a client can just simply restart the process. I'm not super familiar with functions, couldn't a new field be added to Function.Assignment, so that workerId X could be marked as unschedulable.
-Ivan
