You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "nathanschnarr (via GitHub)" <gi...@apache.org> on 2023/06/07 20:21:51 UTC
[GitHub] [druid] nathanschnarr commented on issue #14375: Some Druid overlord API returns 503 when switched from remote to httpRemote for druid.indexer.runner.type
nathanschnarr commented on issue #14375:
URL: https://github.com/apache/druid/issues/14375#issuecomment-1581455719
I ran into this issue as well when attempting to upgrade from v24 to v26, changing from remote to httpRemote and saw the same symptoms.
Additionally, I also tried leaving the value as remote and changing the other flags outlined [here](https://github.com/apache/druid/releases/tag/druid-25.0.0#25-upgrade-segment-discovery) back to their default values. This also manifested as a bunch of 503 errors now in the segments as well as the overlord. I didn't see a path forward onto v26 due to this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org