imply-cheddar opened a new pull request, #13087:
URL: https://github.com/apache/druid/pull/13087
We saw a task with this log in it:
```
2022-09-08T17:01:20,448 ERROR [main-EventThread]
org.apache.druid.curator.CuratorModule - Unhandled error in Curator, stopping
server.
java.lang.NullPointerException: null
at
org.apache.curator.framework.imps.EnsembleTracker.configToConnectionString(EnsembleTracker.java:185)
~[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.EnsembleTracker.processConfigData(EnsembleTracker.java:206)
~[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.EnsembleTracker.access$300(EnsembleTracker.java:50)
~[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.EnsembleTracker$2.processResult(EnsembleTracker.java:150)
~[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:883)
[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:653)
[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.WatcherRemovalFacade.processBackgroundOperation(WatcherRemovalFacade.java:152)
[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.curator.framework.imps.GetConfigBuilderImpl$2.processResult(GetConfigBuilderImpl.java:222)
[curator-framework-4.3.0.jar:4.3.0]
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:598)
[zookeeper-3.5.9.jar:3.5.9]
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510)
[zookeeper-3.5.9.jar:3.5.9]
```
But the server wasn't actually stopped for almost 1.5 hrs. There's perhaps
some sort of race with the startup going on, I'm not sure, but there's also not
really a reason why we need to wait for a graceful shutdown in this instance.
The process is only going to be sad so might as well kill with reckless abandon.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
