Hi - say we have an application using Tranquility to send data to a Druid Indexing Service task. While this is running, we find we need to restart the Overlord and/or Middle Manager processes to deploy an update. This could be a new Druid version, and update to some important config values, etc. We found this document:
Our use case would fall under the Indexing Service Without Autoscaling. Is this really the only way to do it? i.e. send disable POST to Middle Manager and then you have to wait until the current indexing tasks are done (could be an hour or a day depending on settings) so that the indexing tasks for the next time period get scheduled on a different Middle Manager, then you can roll the disabled MM?
What if an index task stops halfway through its time period? Does the index task store any kind of intermediate state on disk that can be recovered/continued if the index task starts up again?