[GitHub] pdeva opened a new issue #6854: downtime when upgrading single node overlord+coordinator to 0.13.0

[GitBox <gi...@apache.org>]

pdeva opened a new issue #6854: downtime when upgrading single node overlord+coordinator to 0.13.0
URL: https://github.com/apache/incubator-druid/issues/6854
 
 
   I noticed this behavior while upgrading from 0.12.3 to 0.13.0.
   We have a single node merged overlord+coordinator.
   
   The assumption is that since overlord/coordinator are not in the query path, upgrading that node shouldn't result in any downtime.
   
   However, it seems when the node restarted (after upgrade), it terminated all existing KIS tasks and restarted them. This tooks a few minutes to happen, and during these 5 minutes or so, no realtime data was available for querying.
   
   I saw a lot of messages like this during the node startup (after upgrade):
   
   ```
   o.a.d.i.c.IndexTaskClient [IndexTaskClient-pctile-hour-0] No TaskLocation available for task [index_kafka_pctile-hour_ec0a9bc8420bc02_ehjdgpfc], this task may not have been assigned to a worker yet or may have already completed
   ```
   
   Is this expected behavior? If so, it might be worth documenting. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org