zeppelin | 0.8.0 |禁用Helium

Question

我们在锁定的企业环境中的docker容器上运行Zeppelin。当Zeppelin启动时，它尝试连接到AWS，一段时间后超时，但成功启动。日志跟踪如下-

 INFO [2018-09-03 14:26:25,131] ({main} Notebook.java[<init>]:128) - Notebook indexing finished: 0 indexed in 0s
 INFO [2018-09-03 14:26:25,133] ({main} Helium.java[loadConf]:103) - Add helium local registry /opt/zeppelin-0.8.0/helium
 INFO [2018-09-03 14:26:25,134] ({main} Helium.java[loadConf]:100) - Add helium online registry https://s3.amazonaws.com/helium-package/helium.json
 WARN [2018-09-03 14:26:25,138] ({main} Helium.java[loadConf]:111) - /opt/zeppelin-0.8.0/conf/helium.json does not exists



ERROR [2018-09-03 14:28:32,864] ({main} HeliumOnlineRegistry.java[getAll]:80) - Connect to s3.amazonaws.com:443 [s3.amazonaws.com/54.231.81.59] failed: Connection timed out
 INFO [2018-09-03 14:28:33,840] ({main} ContextHandler.java[doStart]:744) - Started o.e.j.w.WebAppContext@ef9296d{/,file:/opt/zeppelin-0.8.0/webapps/webapp/,AVAILABLE}{/opt/zeppelin-0.8.0/zeppelin-web-0.8.0.war}
 INFO [2018-09-03 14:28:33,846] ({main} AbstractConnector.java[doStart]:266) - Started ServerConnector@1b1c538d{HTTP/1.1}{0.0.0.0:9991}
 INFO [2018-09-03 14:28:33,847] ({main} Server.java[doStart]:379) - Started @145203ms

我们没有the的用例(到目前为止)，齐柏林飞艇重启的延迟影响了我们。有没有办法禁用这种对we的依赖？

谢谢!

Answer 1

有一个允许不等待亚马逊的PR3082 (ZEPPELIN-3636为亚马逊的s3存储桶端点添加超时)。

PR已合并到master，可能会合并到branch-0.8。