clintropolis commented on issue #10193:
URL: https://github.com/apache/druid/issues/10193#issuecomment-770139706
This timeout and 'forgetting' about a load causes another issue coordinator
side, where if the coordinator decides to try loading the segment on the same
host again after the initial timeout, these type of errors begin appear:
```
2021-01-30T01:48:03,421 WARN [Master-PeonExec--0]
org.apache.druid.server.coordinator.CuratorLoadQueuePeon - ZK node already
exists because segment change request hasn't yet been processed
org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode =
NodeExists for
/druid/loadQueue/localhost:8083/wiki_2016-06-27T00:00:00.000Z_2016-06-28T00:00:00.000Z_2021-01-26T14:05:06.437Z
at
org.apache.zookeeper.KeeperException.create(KeeperException.java:122)
~[zookeeper-3.4.14.jar:3.4.14-4c25d480e66aadd371de8bd2fd8da255ac140bcf]
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
~[zookeeper-3.4.14.jar:3.4.14-4c25d480e66aadd371de8bd2fd8da255ac140bcf]
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:792)
~[zookeeper-3.4.14.jar:3.4.14-4c25d480e66aadd371de8bd2fd8da255ac140bcf]
...
```
until the historical eventually loads the segment (because the now phantom
load order still exists) and deletes the load key, clearing the error.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
