Regarding timeout variable name : I was considering a very specific variable name to allow for a better/future approach to handling this issue - and at that time allow us to retire this variable without potential variable name conflicts (spark.scheduler.blacklistTimeout implies a more general black-list handling, which this is not unfortunately); IMO, this is a stop gap solution until we add support for a better black list approach which handles both executors and blocks.

But until we have that, this will atleast unblock us - thankfully, this is not something which a lot of users are hitting (but is fairly common in our case unfortunately).


Given this, should we expose this in documentation ?