Apologies if a jira exists for this. I could not find one.
It would be very helpful to us to be able to rolling restart (and hopefully rolling upgrade) Impala.
Based on my understanding of impala internals, I think this would require:
- Highly available statestore and catalog. Currently catalog's metadata reload is the long pole in our impala restarts.
- Impalads being able to stop without killing queries they are working on. Most of our queries are short so for us it would be sufficient to give the impala daemon a way to stop taking new work, then restart when it completes all work it has assigned.
|Play nice with load balancers when shutting down coordinator||Open||Unassigned|